Skip to main content
Glama
TylerIlunga

Procore MCP Server

List All Equipment (Deprecated)

list_all_equipment_company
Read-onlyIdempotent

Retrieve a list of all equipment with details for a specified company, enabling discovery of equipment records and lookup of equipment IDs for use in later calls.

Instructions

Return a list of all 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. Use this to discover equipment or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of equipment; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. 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: GET /rest/v1.0/companies/{company_id}/managed_equipment

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.
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.
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: deprecation dates, scheduled removal, company_id defaulting to config value, pagination behavior (page/per_page and response reporting remaining pages), read-only confirmation, and error payload format with common HTTP statuses (401, 403, 404). This exceeds what readOnlyHint and idempotentHint already convey.

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?

The description is dense but every sentence earns its place: purpose, deprecation, usage, pagination, read-only, error handling, required parameters, API category, and endpoint. It is front-loaded with the core purpose and uses clear, structured information without redundancy.

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

Completeness5/5

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

For a tool with 15 parameters and no output schema, the description covers all critical aspects: return format (JSON array), pagination, read-only nature, error scenarios, default behavior, deprecation, and even the endpoint path. It provides enough context for an agent to invoke the tool and understand its response characteristics without needing an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description enhances key parameters: company_id defaults to procore_set_config when omitted, and pagination (page, per_page) is explained with behavior (controls pagination and reports pages remaining). This goes beyond the schema's parameter descriptions, though filters are not individually discussed (schema covers them adequately).

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?

The description clearly states 'Return a list of all Equipment with details for a specified company,' using a specific verb and resource scope. It distinguishes from siblings like list_all_equipment_project by specifying 'company' and from search_all_equipment_company by emphasizing 'all.' The deprecation note and use case ('discover equipment or look up the id') further clarify its role.

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

Usage Guidelines5/5

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

Explicit guidance is provided: 'Use this to discover equipment or to look up the id of one before calling a tool that needs it.' It also gives a clear 'when not to use' by stating it is deprecated and instructing to 'prefer a newer version... and use procore_search_endpoints to find it,' which serves as an explicit alternative-finding directive.

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