Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Available RFIs Locations

list_available_rfis_locations
Read-onlyIdempotent

Retrieve RFI locations for a project to discover available options or find the location ID needed for other Procore tools. Accepts project_id and supports pagination.

Instructions

Returns a list of RFI locations for a specified Project. Use this to discover available RFIs locations or to look up the id of one before calling a tool that needs it. project_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of available RFIs locations; page and per_page control pagination and the response reports how many pages remain. 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. Procore API: Project Management > RFI. Endpoint: GET /rest/v1.0/projects/{project_id}/rfis/filter_options/location_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number for paginated results (default: 1, 1-indexed)
per_pageNoNumber of items per page (default: 100, max: 100)
project_idYesURL path parameter — unique identifier for the project.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds valuable behavior: project_id defaults to procore_set_config, pagination reports pages remaining, and failures carry HTTP status codes (401, 403, 404). This goes well beyond annotation basics.

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 five sentences, each earning its place: purpose, use case, default, pagination, read-only, and error handling. It is logically structured and front-loaded with the primary function.

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

Completeness5/5

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

For a list tool without an output schema, it covers return type (JSON array), pagination behavior, default project_id, and common error responses. This is sufficient for an agent to invoke the tool and interpret results confidently.

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%, so baseline is 3. The description adds meaningful context by explaining that project_id can default to the procore_set_config value and that page/per_page control pagination. However, this conflicts with the schema's required flag for project_id, creating a minor inconsistency.

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 tool 'Returns a list of RFI locations for a specified Project.' This is a specific verb-resource combination that distinguishes it from sibling filter-option tools by focusing on locations and ID lookup.

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?

It explicitly says 'Use this to discover available RFIs locations or to look up the id of one before calling a tool that needs it,' providing a clear when-to-use directive. However, it does not name alternatives or state when not to use, so it lacks explicit exclusion guidance.

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