Procore MCP Server

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

No annotations are provided, so the description must fully disclose behavioral traits. It implies a read-only operation via 'GET' and 'Show', suggesting it is non-destructive, but does not explicitly state safety, permissions, or rate limits. The endpoint format hints at RESTful behavior, but the description lacks details on response format, error handling, or pagination (despite pagination parameters in the schema). This leaves the agent with insufficient context for reliable invocation.

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 with two parts: a tautological title restatement and a technical endpoint. While brief, it is not front-loaded with helpful information for an AI agent; the endpoint details are useful but buried after uninformative text. It avoids redundancy but under-specifies by omitting essential context, making it inefficient in conveying purpose.

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 (a read operation with pagination), lack of annotations, and no output schema, the description is incomplete. It fails to explain what 'Show Company Upload' returns (e.g., upload metadata, file details), behavioral aspects like authentication needs, or how pagination works with the page/per_page parameters. The endpoint hint provides some structure, but overall, the description does not compensate for missing structured data.

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 clear descriptions for all four parameters (company_id, uuid, page, per_page). The description adds no parameter semantics beyond the schema, as it only repeats parameter names in the endpoint template. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description misses an opportunity to clarify parameter relationships or usage.

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 'Show Company Upload' is a tautology that restates the tool name without adding clarity. It includes a technical endpoint '[Core/File Access & Storage] GET /rest/v1.0/companies/{company_id}/uploads/{uuid}', which hints at retrieving a company upload via a GET request, but lacks a clear, plain-language explanation of what the tool does (e.g., 'Retrieve details of a specific file upload for a company'). It does not distinguish this tool from sibling tools, many of which are also 'show' operations for different resources.

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 does not mention prerequisites, such as needing a specific company ID and upload UUID, or contextual cues like when this is appropriate compared to listing uploads or accessing uploads in other contexts. With numerous sibling tools (e.g., 'show_company_upload_v1_1', 'show_project_upload'), the absence of differentiation is a significant gap.

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