Skip to main content
Glama
TylerIlunga

Procore MCP Server

Search All Equipment

search_all_equipment_project

Search and retrieve all equipment records for a project with detailed information. Apply filters to narrow results by criteria such as type, status, or dates.

Instructions

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

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.
search_keywordNoQuery string parameter — search keyword to search Project Managed Equipment.
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?

The description claims both 'Return a list of all searched equipment' and 'Creates a new Field Productivity records', which is contradictory and confusing. Annotations set destructiveHint=false but creation is destructive, implying inconsistency. Behavioral impact (creation vs search) is unclear.

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

Conciseness3/5

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

The description is reasonably concise but contains a contradiction between searching and creating, which wastes clarity. Front-loaded with purpose but then muddled.

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?

The description lacks details about the return format (list vs single object) and does not explain response structure despite 21 parameters. The confusion between search and create leaves the agent uncertain about outcome. Output schema is absent.

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?

Input schema has 21 parameters with 100% schema description coverage. The tool description adds no additional meaning beyond listing one required parameter and the endpoint. Baseline score of 3 is appropriate.

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 the tool returns a list of searched equipment for a specified project, with verb 'search' and resource 'equipment'. It distinguishes from company-level search via the project scope and mentions 'Field Productivity' context.

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 specifies required parameter 'project_id' and provides the HTTP endpoint, but does not compare with siblings like 'search_all_equipment_company' or explain when to use this vs other search tools. No explicit when-not-to-use guidance.

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