Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Checklist List Responsible Contractor Filter Options

list_checklist_list_responsible_contractor_filter_options_2
Read-onlyIdempotent

Retrieve a paginated list of responsible contractor filter options for inspections. Use to find contractor IDs or filter inspection results.

Instructions

List Checklist List Responsible Contractor Filter Options. Use this to enumerate Inspections when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Inspections. Required parameters: project_id. Procore API: Project Management > Inspections. Endpoint: GET /rest/v1.0/projects/{project_id}/checklist/lists/filter_options/responsible_contractors

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. Description adds API endpoint and return type, but no additional behavioral traits beyond what structured fields 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?

Reasonably concise with clear structure, though first sentence repeats the tool name. Includes useful API path and endpoint information.

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?

Sufficient for a simple filter-options tool. With good annotations and full schema, the description covers purpose, required param, and output format. No output schema needed as return type is implied.

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% with detailed parameter descriptions. Description only reiterates required parameter, adding no extra semantic value beyond the 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?

Clearly states it lists responsible contractor filter options for checklist inspections. Mentions pagination and parameter usage. However, it conflates 'enumerate Inspections' with returning filter values, causing slight ambiguity but overall clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context for use (enumerating inspections, pagination, finding IDs) but lacks explicit guidance on when not to use or alternatives among sibling filter tools.

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