Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show External RFI

show_external_rfi
Read-onlyIdempotent

Retrieve a specific external RFI with its complete field set by ID. Uses company and project IDs to fetch read-only data, resolving existing records via list tools first.

Instructions

Returns the specified External RFI. Use this when you already know which external RFI you want and need its full field set. company_id and project_id default to the values 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 external RFI. 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: company_id, project_id, id. Procore API (v2.0): Project Management > RFI. Endpoint: GET /rest/v2.0/companies/{company_id}/projects/{project_id}/external_rfis/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the External RFI
company_idYesURL path parameter — unique identifier for the company.
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

The description reinforces the readOnlyHint by stating 'Read-only — it changes nothing in Procore.' It adds error payload details with common HTTP statuses (401, 403, 404) and the return format (single JSON object), going beyond the annotations.

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 well-structured and front-loaded with purpose, but it redundantly lists 'Required parameters: company_id, project_id, id' when the schema already marks them as required. Minor redundancy prevents a perfect score.

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 simple GET-by-id tool, the description covers purpose, use case, parameter defaults, error behavior, return type, and API endpoint. Given the annotations and schema coverage, it is complete.

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

Parameters5/5

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

Schema descriptions are minimal ('URL path parameter'), but the description adds meaningful context: default behavior for company_id and project_id, and the requirement that id must be resolved via the list tool. This significantly enhances parameter understanding.

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 states 'Returns the specified External RFI,' clearly identifying the verb and resource. It also distinguishes from list tools by noting 'Use this when you already know which external RFI you want and need its full field set.'

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?

Provides explicit when-to-use guidance ('when you already know which external RFI you want') and instructs users to resolve the id with the matching list tool first. Also explains default values for company_id and project_id via procore_set_config, clarifying context.

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