Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Actual Production Quantity

show_actual_production_quantity
Read-onlyIdempotent

Fetch detailed Actual Production Quantity data for a Field Productivity record. Provide project ID, record ID, and quantity to retrieve full details.

Instructions

Return Actual Production Quantity detailed information. Use this to fetch the full details of a specific Field Productivity records by its identifier. Returns a JSON object describing the requested Field Productivity records. Required parameters: project_id, id, quantity. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/projects/{project_id}/actual_production_quantities/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Field Productivity resource
descriptionNoJSON request body field — the description of the Actual Production Quantity
quantityYesJSON request body field — amount installed
crew_idNoJSON request body field — the ID of the crew for the Actual Production Quantity
location_idNoJSON request body field — the Location ID for the Actual Production Quantity
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 and destructiveHint=false. The description adds that it returns a JSON object and required parameters, but does not clarify pagination behavior or the role of the 'quantity' parameter. No contradiction 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 concise (4 sentences), front-loaded with the action and purpose, and each sentence adds value (usage, return type, required params, API reference). No wasted words.

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 basic purpose and required parameters, but lacks explanation of optional parameters (e.g., page, per_page) and their relevance to a single-record fetch. The return type is mentioned generically.

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% with all parameters described. The description merely reiterates the required parameters without adding new meaning or 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 it returns 'detailed information' for a specific Field Productivity record by identifier. It distinguishes itself from sibling tools like 'list_all_actual_production_quantities' by focusing on a single record.

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 says 'Use this to fetch the full details of a specific...record by its identifier,' implying usage for single records. It provides the API module and endpoint, giving context, but does not explicitly state when not to use or mention alternatives.

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