Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Managed Equipment Filter Options

get_managed_equipment_filter_options_project_v1_0_2
Read-onlyIdempotent

Returns managed equipment filter options for incident injury filtering by project ID. Use this to populate filter dropdowns in incident reports.

Instructions

Returns managed equipment in use for filtering injuries. Use this to fetch the full details of a specific Incidents by its identifier. Returns a JSON array of available filter values for Incidents. Required parameters: project_id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/projects/{project_id}/incidents/injuries/filter_options/managed_equipment

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)
Behavior3/5

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

Annotations already declare read-only and idempotent hints. The description adds that it returns a JSON array of filter values, but omits details like pagination behavior or error handling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description contains a redundant sentence and the API endpoint info, making it slightly wordy. Key information is not front-loaded.

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

Completeness2/5

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

No output schema provided, yet the description only vaguely mentions a JSON array. The return values' structure and purpose for filtering injuries are not fully explained. The misleading sentence harms completeness.

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 the schema fully documents parameters. The description only restates that project_id is required, adding no extra meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it returns managed equipment for filtering injuries, which is clear, but contains a contradictory sentence about fetching full incident details. It does not differentiate from sibling filter option tools.

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 other filter options tools. The description includes an inaccurate usage suggestion ('fetch full details of incidents') which could mislead.

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