Skip to main content
Glama
TylerIlunga

Procore MCP Server

Search All Equipment (Deprecated)

search_all_equipment_company

Retrieve detailed equipment lists for a company by applying search filters such as keyword, status, and service dates. Get paginated results with full equipment details.

Instructions

Return a list of all searched equipment with details for a specified company. DEPRECATED: Procore has deprecated this endpoint (as of 2024-12-01). It is scheduled for removal on 2025-12-02; prefer a newer version of this resource where one exists, and use procore_search_endpoints to find it. company_id defaults to the value set by procore_set_config when omitted. Acts on the equipment and returns Procore's response for the operation. 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. Procore API: Project Management > Field Productivity. Endpoint: POST /rest/v1.0/companies/{company_id}/managed_equipment/query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesURL path parameter — unique identifier for the company.
filters__yearNoQuery string parameter — return item(s) with the specified year.
search_keywordNoQuery string parameter — search keyword to search Project Managed Equipment.
filters__statusNoQuery string parameter — returns item(s) matching the specified status value.
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__company_visibleNoQuery string parameter — if true, return item(s) with 'company visible' status.
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.
filters__current_project_idNoQuery string parameter — return item(s) with the specified current project ID.
filters__managed_equipment_idNoQuery string parameter — return item(s) with the specified Managed Equipment ID.
filters__managed_equipment_make_idNoQuery string parameter — return item(s) with the specified Managed Equipment Make ID.
filters__managed_equipment_type_idNoQuery string parameter — return item(s) with the specified Managed Equipment Type ID.
filters__managed_equipment_model_idNoQuery string parameter — return item(s) with the specified Managed Equipment Model ID.
filters__managed_equipment_category_idNoQuery string parameter — return item(s) with the specified Managed Equipment Category ID.
Behavior3/5

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

Annotations already indicate readOnlyHint=false and openWorldHint=true. Description adds deprecation date, error payload statuses (401/403/404), and company_id fallback to procore_set_config. However, it vaguely says 'Acts on the equipment' without clarifying potential side effects or that it is a search/query operation, leaving ambiguity about non-read-only behavior.

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?

Description is information-dense but includes boilerplate 'Acts on the equipment and returns Procore's response for the operation' and some redundancy. Deprecation, default, errors, and endpoint are front-loaded, making it structured but with minor waste.

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

Completeness3/5

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

Given 16 parameters and no output schema, description covers deprecation, authentication errors, defaults, and endpoint. It lacks return format/pagination details, and the vagueness of 'Acts on the equipment' leaves the operation's behavior incomplete for a high-parameter tool.

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?

All 16 parameters are described in the schema (100% coverage), so baseline 3. The description adds default behavior for company_id and marks it required, but does not elaborate on filter semantics or parameter interplay beyond schema.

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?

Description clearly states 'Return a list of all searched equipment with details for a specified company' – a specific verb, resource, and company scope. It also provides the endpoint and API category, distinguishing it from project-scoped versions like search_all_equipment_project.

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?

Explicitly warns the tool is deprecated and directs users to 'prefer a newer version... use procore_search_endpoints to find it.' This is clear alternative guidance. However, it does not explicitly state when to choose this tool over other equipment list/search siblings beyond scope.

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