Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Project Location

show_project_location
Read-onlyIdempotent

Retrieves full details of a specific location in a construction project using the project and location identifiers.

Instructions

Retrieves a Location for a specified project. Use this to fetch the full details of a specific Project records by its identifier. Returns a JSON object describing the requested Project records. Required parameters: project_id, location_id. Procore API: Core > Project. Endpoint: GET /rest/v1.0/projects/{project_id}/locations/{location_id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
location_idYesURL path parameter — unique identifier of the location
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 it read-only and idempotent. The description adds the endpoint and API version but does not disclose pagination behavior or other 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.

Conciseness4/5

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

Relatively concise at four sentences, but includes redundant phrasing ('full details of a specific Project records') that could be streamlined.

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?

Adequate for a simple GET operation given comprehensive annotations and schema, but fails to mention pagination parameters or explain the return format beyond a generic 'JSON object'.

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 already described. The description only restates the required params without adding new meaning or context for optional parameters like page and per_page.

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?

The description clearly states it retrieves a location for a specified project, using a specific verb and resource. However, it later refers to 'Project records' inconsistently, causing mild confusion.

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 versus alternatives. There is no mention of when not to use it or comparisons with sibling tools, leaving usage context entirely implicit.

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