Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Prime Contract Line Item

show_prime_contract_line_item_project
Read-onlyIdempotent

Retrieve full details of a specific line item from a prime contract by providing company, project, prime contract, and line item IDs.

Instructions

Get a specified line item for a given prime contract. Use this to fetch the full details of a specific Prime Contracts by its identifier. Returns a JSON object describing the requested Prime Contracts. Required parameters: company_id, project_id, prime_contract_id, id. Procore API (v2.0): Construction Financials > Prime Contracts. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/prime_contracts/{prime_contract_id}/line_items/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
prime_contract_idYesURL path parameter — unique identifier for the Prime Contract.
idYesURL path parameter — unique identifier of the Prime Contracts resource
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 readOnly, non-destructive, and idempotent hints. Description adds that it returns a JSON object and lists required parameters, but does not disclose additional behavioral traits beyond 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?

Description is concise at 4-5 sentences, front-loaded with the main action, and avoids unnecessary details.

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 read operation with complete annotations and schema, the description provides endpoint info, required parameters, and return type (JSON). Adequate for fetching a single line item.

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 coverage is 100%, so baseline is 3. Description lists required parameters but does not add extra meaning beyond schema descriptions. No details on parameter formats or constraints beyond schema.

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

Purpose4/5

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

Clearly states the tool fetches a specific prime contract line item by its identifier. The title and description are aligned, and the endpoint path distinguishes from v1.0, though it doesn't explicitly differentiate from sibling tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like show_prime_contract_line_item_v1_0. Missing when-not-to-use or prerequisite information.

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