Skip to main content
Glama
TylerIlunga

Procore MCP Server

List All Equipment

list_all_equipment_company
Read-onlyIdempotent

Retrieve a paginated list of all equipment with details for a specified company. Filter by ID, category, type, make, model, status, dates, and more to find specific field productivity records.

Instructions

Return a list of all Equipment with details for a specified company. Use this to enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Field Productivity records. Use page and per_page to control pagination; the response includes pagination metadata. 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
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.
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that the tool returns a paginated JSON array with metadata and mentions pagination controls (page, per_page). It also includes the API endpoint. This adds context beyond annotations but does not reveal any contradictions or hidden behaviors.

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?

The description is a concise paragraph of about six sentences. It front-loads the core purpose and then provides usage guidance, pagination info, required params, and API reference. It is appropriately sized for the complexity of the tool.

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?

Given that there is no output schema, the description clarifies the return type (paginated JSON array of Field Productivity records) and mentions pagination metadata. It also specifies the exact API endpoint. For a list endpoint with many filters, it covers the essential behavioral and structural aspects.

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 mentions that company_id is required and that page/per_page control pagination, but does not detail the many filter parameters beyond 'filter by query parameters'. For a list with 15 parameters, the description could add more value by summarizing common filters, but it does not.

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 explicitly states the tool returns a list of equipment with details for a specified company. It specifies the verb 'Return a list' and the resource 'Equipment with details'. It also mentions 'Field Productivity records' which adds context. Siblings include project-level equipment tools, so this company-level distinction is clear.

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?

The description provides usage scenarios: 'enumerate Field Productivity records when you need a paginated overview, to find IDs, or to filter by query parameters.' It implies when to use this tool. However, it does not explicitly state when not to use it or name alternatives. Given the large number of sibling tools, a brief exclusion would improve clarity.

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