Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Contract Payment

show_contract_payment
Read-onlyIdempotent

Fetch detailed information on a specific contract payment using its ID, project ID, and contract ID.

Instructions

Return detailed information on the specified Contract Payment. Use this to fetch the full details of a specific Commitments by its identifier. Returns a JSON object describing the requested Commitments. Required parameters: id, project_id, contract_id. Procore API: Construction Financials > Commitments. Endpoint: GET /rest/v1.0/contract_payments/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Commitments resource
project_idYesQuery string parameter — unique identifier for the project.
contract_idYesQuery string parameter — unique identifier of the contract
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, indicating a safe read operation. The description adds no new behavioral traits beyond confirming it returns a JSON object, so it does not exceed what annotations provide.

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

Conciseness5/5

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

The description is concise with four sentences, each adding value: purpose, usage guidance, required parameters, and API reference. No superfluous information.

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

Completeness4/5

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

For a simple read tool with full schema coverage, the description covers the essential purpose and required parameters. It does not mention optional pagination parameters (page, per_page), but the schema already describes them, so completeness is high.

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

Parameters3/5

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

Input schema covers all parameters with descriptions (100% coverage). The description only reiterates the required parameters without adding extra semantic context beyond the schema.

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

Purpose5/5

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

The description clearly states the tool returns detailed information on a specified Contract Payment, using a GET endpoint. It distinguishes from list_contract_payments by specifying 'detailed information on the specified' and requiring identifiers.

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

Usage Guidelines3/5

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

The description explains when to use this tool (to fetch full details of a specific Commitment) but does not explicitly mention when not to use it or provide alternatives among siblings such as list_contract_payments.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TylerIlunga/procore-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server