Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Available RFI Status Filter Options

list_available_rfi_status_filter_options
Read-onlyIdempotent

Retrieve status filter options for RFIs on a project to paginate, find IDs, or apply query filters. Returns a JSON array of available filter values.

Instructions

Returns a list of status filter fields and options for RFIs on a specified Project. Use this to enumerate RFI records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for RFI records. Required parameters: project_id. Procore API: Project Management > RFI. Endpoint: GET /rest/v1.0/projects/{project_id}/rfis/filter_options/status

Input Schema

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

Tool Definition Quality

A3.8/5.0
Behavior3/5

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

Annotations already indicate read-only, idempotent, not destructive. Description adds return format (JSON array) and pagination parameters, but no further behavioral details beyond 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?

Two sentences plus metadata are concise and front-loaded. Every sentence serves a purpose without waste.

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

Completeness4/5

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

For a simple read-only tool with annotations and schema coverage, the description covers purpose, usage, parameters, and return type. Lacks only example of response values.

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 covers all three parameters with descriptions. Description only mentions required parameter and pagination implicitly, adding minimal value beyond schema.

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 returns status filter options for RFIs on a project, but incorrectly says 'enumerate RFI records' which is slightly off since it enumerates filter options, not records.

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?

Provides clear usage context: when to use, required parameters, pagination, and API endpoint. Does not explicitly exclude alternatives but distinguishes from sibling filter tools via name.

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