Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Show First Prime Contract

show_first_prime_contract
Read-onlyIdempotent

Fetches the first prime contract for a specified project and returns its complete field set as a single JSON object. Use this read-only tool when you need the initial contract details.

Instructions

Returns the first Prime Contract created for the specified Project. Use the /prime_contracts endpoint if you need to return more than one Prime Contract. Use this when you already know which first prime contract you want and need its full field set. Returns a single JSON object describing the first prime contract. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: project_id. Procore API: Construction Financials > Prime Contracts. Endpoint: GET /rest/v1.0/prime_contract

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already mark this as read-only and non-destructive. The description adds value by disclosing the return format ('single JSON object') and error payload behavior with common HTTP status codes (401, 403, 404). This goes beyond the annotation hints.

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

Conciseness4/5

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

The description is front-loaded with the core purpose, followed by usage guidance, behavior, parameters, and API reference. It is somewhat verbose but every segment provides useful context, with only minor redundancy around the tool's usage.

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

Completeness5/5

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

For a single-parameter fetch tool, the description covers all key aspects: purpose, endpoint, required parameter, return type, read-only guarantee, and error statuses. No output schema is present, but the return description suffices.

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?

Schema already covers the single parameter with a clear description ('unique identifier for the project'), and schema coverage is 100%. The description only restates that project_id is required, adding no new semantics 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 opens with a specific verb+resource: 'Returns the first Prime Contract created for the specified Project.' It clearly distinguishes this show operation from list operations by stating it returns a single JSON object and contrasting with the `/prime_contracts` endpoint for multiple contracts.

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

Usage Guidelines5/5

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

It explicitly directs users to the `/prime_contracts` endpoint when more than one contract is needed and specifies to use this tool when the first contract's full field set is required. This provides clear when-to-use and an explicit alternative.

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