Skip to main content
Glama
TylerIlunga

Procore MCP Server

List All Equipment

list_all_equipment_project
Read-onlyIdempotent

Retrieve a paginated list of all managed equipment details for a specified project. Use to find equipment IDs, filter by categories, status, or dates, and control pagination with page and per_page parameters.

Instructions

Return a list of all equipment with details for a specified project. 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: project_id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/projects/{project_id}/managed_equipment

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
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.
filters__onsiteNoQuery string parameter — onsite Dates. Returns item(s) with the specified range of onsite dates.
filters__offsiteNoQuery string parameter — offsite Dates. Returns item(s) with the specified range of offsite dates.
filters__ownershipNoQuery string parameter — returns only item(s) with the specified ownership value. Must be one of Owned, Rented, or Sub.
filters__vendor_idNoQuery string parameter — return item(s) with the specified Vendor ID.
filters__induction_statusNoQuery string parameter — returns item(s) with the specified inudction status.
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds minimal behavioral context (pagination returns) but does not disclose additional traits beyond annotations.

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 about 80 words with three sentences. It is front-loaded with purpose but includes extra details like API endpoint and Procore section, which add length. Still efficient.

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 20 parameters with full schema descriptions and no output schema, the description covers the main use case (list equipment with pagination and filters). It does not explain return format in depth but is sufficient for read operation.

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% with descriptions for all 20 parameters. Description only mentions project_id, page, per_page without adding new meaning beyond the schema, so baseline score of 3.

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

Purpose4/5

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

The description clearly states it returns a list of equipment for a specific project, with details. It specifies the verb 'return' and resource 'equipment', but does not explicitly differentiate from sibling tools like list_all_equipment_company.

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

Usage Guidelines3/5

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

The description says to use when needing a paginated overview or to filter, implying usage context, but does not provide explicit when-not-to-use or mention alternatives from the sibling list.

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