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 states 'Update app installation', which implies a mutation operation, but lacks critical details: it does not specify required permissions, whether the update is partial or full, potential side effects (e.g., app reconfiguration), error conditions, or response format. The endpoint hint suggests a PATCH method, implying partial updates, but this is not explained. The description is minimal and misses key behavioral traits.

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 brief purpose statement and technical endpoint details. It is front-loaded with the core action ('Update app installation'), but the technical details (platform and endpoint) could be considered extraneous for an AI agent. However, it avoids redundancy and is efficiently structured in a single line, earning a high score for brevity.

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 required parameters, including a nested object) and lack of annotations and output schema, the description is incomplete. It does not address what the tool returns, error handling, or the scope of updates. For a mutation tool with significant parameters, the description should provide more context about behavior and outcomes, but it falls short, leaving the agent with insufficient guidance.

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 documented in the schema (e.g., 'id' as 'App installation ID', 'app_installation' as 'app_installation'). The description adds no parameter semantics beyond what the schema provides—it does not explain the purpose of 'app_installation' object or the mutual exclusivity of 'project_id' and 'company_id'. Given the high schema coverage, the baseline score of 3 is appropriate, as the description does not compensate but also does not detract.

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 'Update app installation' is a tautology that restates the tool name without adding specificity. It mentions the platform/endpoint ('[Platform - Developer Tools/App Marketplace] PATCH /rest/v1.0/app_installations/{id}'), but this is technical detail rather than clarifying the functional purpose (e.g., what aspects of an app installation are updated, such as permissions, settings, or status). It does not distinguish from sibling tools like 'create_app_installation' or 'show_app_installation' beyond the verb 'update'.

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 (e.g., an existing app installation ID), exclusions, or related tools like 'create_app_installation' or 'show_app_installation'. The agent must infer usage solely from the tool name and schema, with no explicit context from the description.

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