Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Project Stage

show_project_stage
Read-onlyIdempotent

Retrieve detailed information about a specific project stage by providing the company ID and stage ID, including stage name and associated settings.

Instructions

Show detail on a specified Project Stage. Use this to fetch the full details of a specific Company Settings by its identifier. Returns a JSON object describing the requested Company Settings. Required parameters: company_id, id. Procore API: Company Admin > Company Settings. Endpoint: GET /rest/v1.0/companies/{company_id}/project_stages/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — iD of the project stage
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. The description adds context about being a GET endpoint but contains a factual error by referencing 'Company Settings' instead of 'Project Stage'. This misrepresentation harms transparency and could mislead the agent.

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

Conciseness3/5

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

The description provides API endpoint and required parameters but includes redundant or inaccurate information (e.g., 'Company Settings'). It is neither highly concise nor overly verbose, but the error degrades structure.

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

Completeness2/5

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

For a simple read operation, the description should accurately define the resource. The mislabeling of the object as 'Company Settings' instead of 'Project Stage' is a significant gap. Without an output schema, the description does not adequately compensate.

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 parameters are fully documented in the schema. The description only repeats the required parameters without adding extra meaning, meeting the baseline for high coverage.

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

Purpose3/5

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

The description states 'Show detail on a specified Project Stage' which clearly identifies the action and resource. However, it later incorrectly refers to 'Company Settings', causing confusion and reducing clarity. The verb and primary noun are clear, but the misstatement detracts.

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 is provided on when to use this tool versus sibling tools. The description only lists required parameters and API details, but fails to differentiate from other show tools or specify conditions for use.

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