# Build the Year MCP

Build the Year MCP is the governed interface to event-led revenue intelligence. Reads share the product ledger. Writes stop at preview or propose; humans approve and commit.
Governed reads carry confidence, policy, and provenance. Chapter-isolated capabilities remain bound to their Chapter context.
Scenario outputs never mutate planned or committed capacity.

MCP endpoint: https://api.buildtheyear.com/mcp
Live capabilities: https://api.buildtheyear.com/api/v1/mcp/capabilities
Human documentation: https://www.buildtheyear.com/mcp
Static catalog: https://www.buildtheyear.com/mcp/catalog.json
Robot reference: https://www.buildtheyear.com/llms-mcp.txt
Discovery pointer: https://www.buildtheyear.com/.well-known/mcp.json

# Tools

## Calculate True ROI (`calculate_true_roi`)
URL: https://www.buildtheyear.com/mcp/tools/calculate-true-roi
Job: justify-spend
Output type: deterministic
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use for governed event or portfolio ROI, fully-loaded cost, and cost-per-pipeline-dollar questions.
Inputs:
  - eventId: string; optional
  - period: string; optional; values Q1 | Q2 | Q3 | Q4 | year
  - year: number; optional
  - includeCapacityCost: boolean; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - What was the True ROI of this event?
  - Which events justified their spend?

## Get Recommendations (`get_recommendations`)
URL: https://www.buildtheyear.com/mcp/tools/get-recommendations
Job: justify-spend, choose-better-mix, force-gtm-follow-through
Output type: heuristic
Write contract: read only
Governance: recommendation_scoring, attribution
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use when a governed portfolio diagnosis must end in a named action and quantified impact.
Inputs:
  - period: string; optional; values Q1 | Q2 | Q3 | Q4 | year
  - year: number; optional
  - types: string[]; optional; values cut_zero_yield | cut_negative_roi | shift_timing | tier_rebalance | tier_invest | followup_leakage | outsource_signal | data_coverage
  - limit: number; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - What should we change in the portfolio?
  - Where are we leaking value?

## Generate CFO Report (`generate_cfo_report`)
URL: https://www.buildtheyear.com/mcp/tools/generate-cfo-report
Job: justify-spend
Output type: deterministic
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use for a governed executive or board summary of event-led revenue performance.
Inputs:
  - period: string; optional
  - year: number; optional
  - format: string; optional; values executive_summary | full
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Create the CFO report for this quarter.
  - How should I explain event performance to finance?

## Compare Events (`compare_events`)
URL: https://www.buildtheyear.com/mcp/tools/compare-events
Job: justify-spend, choose-better-mix
Output type: deterministic
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use to compare a known set of events on governed performance dimensions.
Inputs:
  - eventIds: string[]; required
  - dimensions: string[]; optional; values roi | cost | pipeline | yield | capacity | attendance
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - How did these events compare?
  - Which event performed best on yield?

## Find Similar Events (`find_similar_events`)
URL: https://www.buildtheyear.com/mcp/tools/find-similar-events
Job: choose-better-mix
Output type: heuristic
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use to find historical analogues for a reference event.
Inputs:
  - eventId: string; required
  - dimensions: string[]; optional; values tier | format | region | budget_range
  - limit: number; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Which events are most like this one?
  - Find comparable events for planning.

## Explain Variance (`explain_variance`)
URL: https://www.buildtheyear.com/mcp/tools/explain-variance
Job: justify-spend
Output type: heuristic
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use when a specific event metric changed or missed expectation and governed causes are needed.
Inputs:
  - eventId: string; required
  - metric: string; required; values budget | pipeline | attendance | roi
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Why did this event miss budget?
  - What caused the ROI variance?

## Analyze Portfolio Yield (`analyze_portfolio_yield`)
URL: https://www.buildtheyear.com/mcp/tools/analyze-portfolio-yield
Job: choose-better-mix
Output type: deterministic
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use for governed Portfolio Yield trends and mix efficiency.
Inputs:
  - period: string; optional; values Q1 | Q2 | Q3 | Q4 | year
  - year: number; optional
  - breakdown: string; optional; values tier | format | region | all
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - How is Portfolio Yield trending?
  - Which tiers produce the most pipeline per hour?

## Identify Anomalies (`identify_anomalies`)
URL: https://www.buildtheyear.com/mcp/tools/identify-anomalies
Job: justify-spend, choose-better-mix
Output type: associative
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use to detect outlier events that merit investigation, not to assert causation.
Inputs:
  - threshold: string; optional; values moderate | significant | critical
  - categories: string[]; optional; values cost | pipeline | attendance | roi
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Which events are unusual?
  - Where are the cost or ROI outliers?

## Calculate Outsourcing Case (`calculate_outsourcing_case`)
URL: https://www.buildtheyear.com/mcp/tools/calculate-outsourcing-case
Job: choose-better-mix
Output type: scenario
Write contract: read only
Governance: outsourcing, capacity
Scope: chapter-isolated
Role: admin
Do not: Do not present the scenario as committed capacity, apply it, or treat salary assumptions as actuals.
When to use: Use to preview an outsourcing business case without changing planned or committed capacity.
Inputs:
  - year: number; optional
  - tiers: string[]; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Should we outsource part of the event portfolio?
  - What is the outsourcing break-even?

## Generate Headcount Case (`generate_headcount_case`)
URL: https://www.buildtheyear.com/mcp/tools/generate-headcount-case
Job: justify-spend, choose-better-mix
Output type: scenario
Write contract: read only
Governance: headcount_justification, capacity
Scope: chapter-isolated
Role: admin
Do not: Do not present the scenario as an approved hire, apply it to committed capacity, or treat salary assumptions as actuals.
When to use: Use to preview a staffing scenario and its governed business case.
Inputs:
  - year: number; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Do we need another FTE?
  - Build a headcount justification.

## Analyze Resource Capacity (`analyze_resource_capacity`)
URL: https://www.buildtheyear.com/mcp/tools/analyze-resource-capacity
Job: choose-better-mix
Output type: deterministic
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use for year-specific resource utilization and policy-classified overtime risk.
Inputs:
  - resourceId: string; optional
  - year: number; required
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - Who is over capacity?
  - Where is overtime risk concentrated?

## List Governed Proposals (`list_governed_proposals`)
URL: https://www.buildtheyear.com/mcp/tools/list-governed-proposals
Job: force-gtm-follow-through
Output type: deterministic
Write contract: read only
Governance: governed_writes
Scope: chapter-isolated
Role: member
Do not: Do not expose proposal payloads, cross Chapter boundaries, approve, reject, resume, or commit.
When to use: Use to inspect Chapter-scoped governed proposal status and audit history.
Inputs:
  - status: string; optional; values pending_approval | approved | committing | committed | rejected | expired | failed
  - action_type: string; optional
  - limit: number; optional
  - cursor: string; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - What governed proposals are pending?
  - Show recent Decision History.

## Sync Templates (`sync_templates`)
URL: https://www.buildtheyear.com/mcp/tools/sync-templates
Job: choose-better-mix
Output type: deterministic
Write contract: preview/propose only; human approve and human commit required
Governance: governed_writes, capacity
Scope: chapter-isolated
Role: admin
Do not: Do not approve, reject, resume, commit, or directly mutate event allocations; MCP is preview/propose only.
When to use: Use preview first, then propose a template synchronization for human approval and commit.
Inputs:
  - action: string; required; values preview | propose
  - tier_id: string; required
  - event_type_id: string; required
  - event_format_id: string; required
Question patterns:
  - Preview template synchronization.
  - Propose applying updated tier role templates.

## Propose Wrap-Up Completion (`propose_wrap_up_completion`)
URL: https://www.buildtheyear.com/mcp/tools/propose-wrap-up-completion
Job: force-gtm-follow-through
Output type: deterministic
Write contract: preview/propose only; human approve and human commit required
Governance: governed_writes, event_lifecycle
Scope: chapter-isolated
Role: admin
Do not: Do not approve, reject, resume, commit, or directly update the event; MCP is preview/propose only.
When to use: Use to preview eligibility or propose event wrap-up completion for distinct-human approval.
Inputs:
  - action: string; required; values preview | propose
  - event_id: string; required
Question patterns:
  - Can this event be wrapped up?
  - Propose completing this event wrap-up.

## Propose Capacity Decision (`propose_capacity_decision`)
URL: https://www.buildtheyear.com/mcp/tools/propose-capacity-decision
Job: choose-better-mix
Output type: deterministic
Write contract: preview/propose only; human approve and human commit required
Governance: governed_writes, capacity
Scope: chapter-isolated
Role: admin
Do not: Do not approve, reject, resume, commit, alter allocations, apply scenarios, or change committed capacity; MCP is preview/propose only.
When to use: Use to preview or record a proposed monthly capacity disposition without mutating capacity.
Inputs:
  - action: string; required; values preview | propose
  - year: number; required
  - month: number; required
  - disposition: string; required; values accept_risk | will_rebalance | escalate
  - note: string; optional
Question patterns:
  - Preview a capacity decision.
  - Propose acknowledging this month’s capacity risk.

## Identify Portfolio Patterns (`identify_portfolio_patterns`)
URL: https://www.buildtheyear.com/mcp/tools/identify-portfolio-patterns
Job: justify-spend, choose-better-mix
Output type: associative
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use to explore recurring portfolio correlations without claiming causation.
Inputs:
  - metric: string; required; values roi | yield | cost_efficiency | pipeline
  - period: string; optional; values Q1 | Q2 | Q3 | Q4 | year
  - year: number; optional
  - minEvents: number; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - What patterns distinguish high performers?
  - What correlates with strong yield?

## Compare Periods (`compare_periods`)
URL: https://www.buildtheyear.com/mcp/tools/compare-periods
Job: justify-spend, choose-better-mix
Output type: associative
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use to compare two governed portfolio periods and name the drivers of change.
Inputs:
  - currentPeriod: string; required; values Q1 | Q2 | Q3 | Q4 | year
  - currentYear: number; required
  - previousPeriod: string; required; values Q1 | Q2 | Q3 | Q4 | year
  - previousYear: number; required
  - dimensions: string[]; optional; values pipeline | cost | yield | mix | capacity
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - What changed quarter over quarter?
  - Why did portfolio performance move?

## Optimize Tier Mix (`optimize_tier_mix`)
URL: https://www.buildtheyear.com/mcp/tools/optimize-tier-mix
Job: choose-better-mix
Output type: heuristic
Write contract: read only
Governance: capacity, attribution
Scope: chapter-isolated
Role: member
Do not: Do not apply the recommendation, change committed capacity, or present historical averages as guaranteed outcomes.
When to use: Use for an indicative tier-mix recommendation under explicit capacity and optional budget constraints.
Inputs:
  - totalCapacityHours: number; required
  - totalBudget: number; optional
  - targetPipeline: number; optional
  - fixedEvents: string[]; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - What tier mix maximizes Portfolio Yield?
  - How should we allocate constrained capacity?

## Portfolio Health Check (`portfolio_health_check`)
URL: https://www.buildtheyear.com/mcp/tools/portfolio-health-check
Job: justify-spend, choose-better-mix, force-gtm-follow-through
Output type: heuristic
Write contract: read only
Governance: portfolio_health, attribution, capacity
Scope: chapter-isolated
Role: member
Do not: Do not treat scenario, planned, committed, and actual values as interchangeable or bypass governed provenance.
When to use: Use for a broad governed portfolio diagnosis and prioritized action list.
Inputs:
  - period: string; optional; values Q1 | Q2 | Q3 | Q4 | year
  - year: number; optional
  - verbosity: string; optional; values summary | standard | detailed
Question patterns:
  - How healthy is the portfolio?
  - What are the portfolio red flags?

# Resources

## Server Health (`bty://health`)
URL: https://www.buildtheyear.com/mcp/resources/health
Job: None
Output type: deterministic resource
Write contract: read only
Governance: None
Scope: org-global
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to confirm the MCP server is reachable and identify the current organization context before other reads.
URI variables:
  - None

## BTY Context (`bty://context`)
URL: https://www.buildtheyear.com/mcp/resources/context
Job: justify-spend, choose-better-mix, force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: viewer
MIME: text/markdown
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use at the start of an MCP session to orient on Chapter-bound policies, portfolio performance, confidence, integrations, and available capabilities.
URI variables:
  - None

## Organization Overview (`bty://org/overview`)
URL: https://www.buildtheyear.com/mcp/resources/org-overview
Job: justify-spend, choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use for a concise health snapshot of organization KPIs, attribution policy, data confidence, capacity, and connected systems.
URI variables:
  - None

## Events List (`bty://events`)
URL: https://www.buildtheyear.com/mcp/resources/events-list
Job: justify-spend, choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to enumerate events, scan key metrics and totals, or obtain an event ID before opening detail resources.
URI variables:
  - None

## Event Detail (`bty://events/{eventId}`)
URL: https://www.buildtheyear.com/mcp/resources/event-detail
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use when you need one event's full governed ledger record, True ROI, and provenance summary.
URI variables:
  - eventId: string; required

## Event Costs (`bty://events/{eventId}/costs`)
URL: https://www.buildtheyear.com/mcp/resources/event-costs
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to reconcile one event's budget, actual cost, variance, and capacity hours.
URI variables:
  - eventId: string; required

## Event Outcomes (`bty://events/{eventId}/outcomes`)
URL: https://www.buildtheyear.com/mcp/resources/event-outcomes
Job: justify-spend, force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to inspect one event's pipeline influence, attributed revenue, and linked opportunities.
URI variables:
  - eventId: string; required

## Event KPIs (`bty://events/{eventId}/kpis`)
URL: https://www.buildtheyear.com/mcp/resources/event-kpis
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to evaluate one event's True ROI, cost per lead, yield, and metric confidence.
URI variables:
  - eventId: string; required

## Event Provenance (`bty://events/{eventId}/provenance`)
URL: https://www.buildtheyear.com/mcp/resources/event-provenance
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: admin
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to audit the field-level source behind a tracked event value.
URI variables:
  - eventId: string; required

## Event Changelog (`bty://events/{eventId}/changelog`)
URL: https://www.buildtheyear.com/mcp/resources/event-changelog
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: None
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to review when an event changed and which provenance or activity records document the change.
URI variables:
  - eventId: string; required

## Portfolio Yield (`bty://portfolio/yield`)
URL: https://www.buildtheyear.com/mcp/resources/portfolio-yield
Job: choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to assess pipeline generated per capacity hour across tiers and compare portfolio periods.
URI variables:
  - None

## Portfolio ROI (`bty://portfolio/roi`)
URL: https://www.buildtheyear.com/mcp/resources/portfolio-roi
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: attribution, capacity
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to evaluate overall True ROI and identify top, bottom, or tier-level portfolio performance.
URI variables:
  - None

## Portfolio Recommendations (`bty://portfolio/recommendations`)
URL: https://www.buildtheyear.com/mcp/resources/portfolio-recommendations
Job: justify-spend, choose-better-mix, force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: recommendation_scoring
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use when portfolio facts must resolve into governed actions with diagnosis, impact, and audit links.
URI variables:
  - None

## Portfolio Capacity (`bty://portfolio/capacity`)
URL: https://www.buildtheyear.com/mcp/resources/portfolio-capacity
Job: choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use for a current-year portfolio summary of total hours, utilization, and resource count.
URI variables:
  - None

## Portfolio Capacity by Year (`bty://portfolio/capacity/{year}`)
URL: https://www.buildtheyear.com/mcp/resources/portfolio-capacity-year
Job: choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to retrieve portfolio hours, utilization, and resource count for a specified year.
URI variables:
  - year: number; required

## Attribution Policy (`bty://policies/attribution`)
URL: https://www.buildtheyear.com/mcp/resources/policies-attribution
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to verify the attribution metric, window, and touch model governing pipeline and ROI results.
URI variables:
  - None

## Custom Field Definitions (`bty://custom-fields/definitions`)
URL: https://www.buildtheyear.com/mcp/resources/custom-fields-definitions
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: None
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to discover organization-defined event fields, their types, allowed values, and confidence defaults.
URI variables:
  - None

## Event Custom Fields (`bty://custom-fields/events/{eventId}`)
URL: https://www.buildtheyear.com/mcp/resources/custom-fields-event
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: None
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to read governed custom-field values and provenance for one event after discovering the field definitions.
URI variables:
  - eventId: string; required

## Capacity Report (`bty://reports/capacity/{year}`)
URL: https://www.buildtheyear.com/mcp/resources/reports-capacity
Job: choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use for a year-specific monthly capacity report with per-resource utilization, overtime risk, and projected overtime cost.
URI variables:
  - year: number; required

## Budget Report (`bty://reports/budget/{year}`)
URL: https://www.buildtheyear.com/mcp/resources/reports-budget
Job: justify-spend
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to compare planned and actual spend by month for a specified year and inspect variance.
URI variables:
  - year: number; required

## Events Report (`bty://reports/events/{year}`)
URL: https://www.buildtheyear.com/mcp/resources/reports-events
Job: justify-spend, choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to compare planned and committed hours, budget, actuals, and variance across events for a specified year.
URI variables:
  - year: number; required

## Resources Report (`bty://reports/resources/{year}`)
URL: https://www.buildtheyear.com/mcp/resources/reports-resources
Job: choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to compare annual hours, utilization, event load, and estimated labor cost across resources for a specified year.
URI variables:
  - year: number; required

## Resource Assignments (`bty://resources/{resourceId}/assignments`)
URL: https://www.buildtheyear.com/mcp/resources/resource-assignments
Job: choose-better-mix
Output type: deterministic resource
Write contract: read only
Governance: capacity
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to list every event assignment, role, and event detail for one known resource ID.
URI variables:
  - resourceId: string; required

## Active Chapter (`bty://chapter`)
URL: https://www.buildtheyear.com/mcp/resources/chapter
Job: justify-spend, choose-better-mix, force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: None
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to confirm the active Chapter identity and organization relationship that bounds the current MCP session.
URI variables:
  - None

## Integration Chapter Status (`bty://integrations/chapter-status`)
URL: https://www.buildtheyear.com/mcp/resources/integration-chapter-status
Job: force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: attribution
Scope: chapter-isolated
Role: viewer
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to diagnose provider health and Chapter CRM campaign-mapping coverage before following up on integration gaps.
URI variables:
  - None

## Decision History (`bty://governance/proposals`)
URL: https://www.buildtheyear.com/mcp/resources/governance-proposals
Job: force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: governed_writes
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to page through Chapter-scoped governed proposals and inspect their lifecycle status.
URI variables:
  - None

## Decision History Entry (`bty://governance/proposals/{proposalId}`)
URL: https://www.buildtheyear.com/mcp/resources/governance-proposal-detail
Job: force-gtm-follow-through
Output type: deterministic resource
Write contract: read only
Governance: governed_writes
Scope: chapter-isolated
Role: member
MIME: application/json
Do not: Do not infer missing tenant data, remove governance labels, or combine Chapter data outside the bound context.
When to use: Use to audit one known Chapter-scoped governed proposal's approval and commit evidence.
URI variables:
  - proposalId: string; required