Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Budget Line Item

show_budget_line_item
Read-onlyIdempotent

Fetch detailed budget line item data by providing its unique identifier and project ID. Returns a JSON object with full budget record details.

Instructions

Return information about a Budget Line Item. Use this to fetch the full details of a specific Budget records by its identifier. Returns a JSON object describing the requested Budget records. Required parameters: id, project_id. Procore API (v1.1): Construction Financials > Budget. Endpoint: GET /rest/v1.1/budget_line_items/{id}

Input Schema

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

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value by specifying the HTTP method (GET), API version, and endpoint, and confirming the response is a JSON object. No contradictions with annotations.

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 three sentences, each providing key information: purpose, usage, response type, required parameters, and API details. No unnecessary words, and the most important information is front-loaded.

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

Completeness3/5

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

The description covers the main purpose and required parameters but lacks explanation of the optional pagination parameters (page, per_page) and does not fully clarify the structure of the response (e.g., single object vs. list). Given no output schema, more detail on the response shape would be helpful.

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 all parameters are described. The description reiterates that id and project_id are required but doesn't add extra meaning beyond the schema. The optional page/per_page parameters are not explained in the description.

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 action ('Return information about a Budget Line Item') and the resource ('Budget Line Item'). It specifies fetching full details by identifier, distinguishing it from sibling CRUD and list tools.

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

Usage Guidelines4/5

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

The description indicates when to use the tool (to fetch full details by identifier) but does not explicitly exclude listing or provide alternatives. The usage is clear from context, but no direct comparison to siblings.

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