Procore MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states it's a GET operation, implying it's a read-only tool, but doesn't confirm this explicitly. It doesn't mention potential side effects, authentication requirements, rate limits, error conditions, or what the response looks like (e.g., paginated list of exchange rates). The API path hints at resource structure but lacks behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise but under-specified. It includes the tool name, a category hint '[Construction Financials/Currency Configurations]', and the API endpoint. However, it's not front-loaded with clear purpose; the endpoint details might clutter understanding. It wastes no words but could be more structured to highlight key information first.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (5 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what 'exchange rates' are in this context, how they're used, or what the output contains. Without annotations or output schema, the agent lacks critical information about the tool's behavior and results. The description should provide more context to compensate for these gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all parameters well-documented in the schema (e.g., company_id, project_id, include_inactive, page, per_page). The description adds no additional parameter semantics beyond what the schema provides. It doesn't explain the purpose of include_inactive (e.g., to show historical rates) or pagination behavior. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but doesn't detract either.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get Project Exchange Rates' is a tautology that restates the tool name without adding clarity. It mentions the API endpoint path '[Construction Financials/Currency Configurations] GET /rest/v1.0/companies/{company_id}/projects/{project_id}/currency_configuration/exchange_rates', which provides some context but doesn't clearly explain what the tool does beyond the name. It lacks specificity about what 'exchange rates' refer to (e.g., currency conversion rates for financial transactions) and doesn't distinguish it from sibling tools like 'get_company_exchange_rates' or 'create_project_exchange_rates'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention any prerequisites, such as needing a valid company and project ID, or when to use it over other exchange rate-related tools (e.g., 'get_company_exchange_rates' for company-level rates). There's no indication of typical use cases or constraints, leaving the agent with no usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.