Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Quantity Logs

show_quantity_logs
Read-onlyIdempotent

Retrieve a specific quantity log by ID to obtain its complete field set. This read-only action provides full details without altering Procore data.

Instructions

Returns single Quantity Log. Use this when you already know which quantity log you want and need its full field set. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the quantity log. 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, id. Procore API: Project Management > Daily Log. Endpoint: GET /rest/v1.0/projects/{project_id}/quantity_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Daily Log resource
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

Beyond annotations, the description adds concrete behavioral details: it is read-only, returns a single JSON object, and describes likely error status codes (401, 403, 404) with their meanings. This goes beyond the basic readOnlyHint and destructiveHint flags.

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 longer than necessary but well-organized, starting with purpose, then usage, return type, safety, errors, and endpoint. Each sentence adds information, but some redundancy exists (e.g., 'Returns a single JSON object' and listing required parameters again).

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?

With no output schema, the description compensates by stating it returns full field set, covers error cases, and provides the endpoint. It could describe the response fields in more detail, but for a simple show tool the information is adequate.

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

Parameters4/5

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

Schema coverage is 100% with basic type/description for both parameters. The description adds context by explaining that id must identify an existing parent record and can be resolved via the list tool, and mention of project_id default behavior (though slightly confusing given it is required). This meaningfully enhances 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 'Returns single Quantity Log' with a specific verb and resource, and distinguishes itself from the list tool by indicating it returns the full field set for a known quantity log. The use case is explicit.

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 says to use this when you already know the quantity log and need the full field set, and instructs to resolve the id with the matching list tool first. This differentiates it from list operations.

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