Skip to main content
Glama
TylerIlunga

Procore MCP Server

Search All Equipment

search_all_equipment_company

Search all managed equipment for a company, returning details like category, type, make, model, and service dates. Requires a company ID.

Instructions

Return a list of all searched equipment with details for a specified company. Use this to perform the search all action on Field Productivity records. Creates a new Field Productivity records and returns the created object on success (HTTP 201). Required parameters: company_id. Procore API: Project Management > Field Productivity. Endpoint: POST /rest/v1.0/companies/{company_id}/managed_equipment/query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
filters__managed_equipment_idNoQuery string parameter — return item(s) with the specified Managed Equipment ID.
filters__managed_equipment_category_idNoQuery string parameter — return item(s) with the specified Managed Equipment Category ID.
filters__managed_equipment_type_idNoQuery string parameter — return item(s) with the specified Managed Equipment Type ID.
filters__managed_equipment_make_idNoQuery string parameter — return item(s) with the specified Managed Equipment Make ID.
filters__managed_equipment_model_idNoQuery string parameter — return item(s) with the specified Managed Equipment Model ID.
filters__company_visibleNoQuery string parameter — if true, return item(s) with 'company visible' status.
filters__current_project_idNoQuery string parameter — return item(s) with the specified current project ID.
filters__yearNoQuery string parameter — return item(s) with the specified year.
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
filters__last_service_dateNoQuery string parameter — return item(s) with a last service date within the specified ISO 8601 datetime range.
filters__next_service_dateNoQuery string parameter — return item(s) with a next service date within the specified ISO 8601 datetime range.
search_keywordNoQuery string parameter — search keyword to search Project Managed Equipment.
Behavior1/5

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

The description mentions 'Creates a new Field Productivity records', implying a write operation. Annotations have readOnlyHint=false and destructiveHint=false, which do not directly contradict but are misleading. The creation claim is highly suspicious for a search tool and lacks clarification.

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

Conciseness2/5

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

The description is short but contains contradictory statements (search vs create). This undermines clarity and wastes the user's time. Could be concise if corrected.

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 exists, so the description should explain search behavior, pagination, and filtering. It only vaguely mentions 'all searched equipment' and does not elaborate on filters or pagination parameters that are present in the schema.

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 baseline is 3. The description only reiterates the required company_id and mentions the endpoint method (POST), adding minimal value beyond the schema.

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

Purpose2/5

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

The description claims to 'Return a list of all searched equipment' (search), but then states 'Creates a new Field Productivity records' (create). This contradiction makes the tool's purpose unclear. The name suggests search, but the description introduces write behavior.

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?

Provides minimal guidance: states required parameter company_id and API endpoint. No mention of when not to use this tool or alternatives. The contradictory creation statement further confuses usage 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