Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Equipment By Project (Project)

get_equipment_by_project_project
Read-onlyIdempotent

Retrieve a paginated list of equipment records for a specific project, with filters for type, make, model, and more.

Instructions

Get equipment by project (Project). Use this to fetch the full details of a specific Equipment records by its identifier. Returns a paginated JSON array of Equipment records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id, per_page, company_id. Procore API (v2.1): Core > Equipment. Endpoint: GET /rest/v2.1/companies/{company_id}/projects/{project_id}/equipment_register

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — the Id of the project
company_idYesURL path parameter — unique identifier for the company.
searchNoQuery string parameter — search criteria applied on name, identification number and serial number
filters__idNoQuery string parameter — filter results by id
filters__association_statusNoQuery string parameter — the status of association. Values can be 'current', 'past' or 'all'. Default is 'current'
filters__typeNoQuery string parameter — filter results by type
filters__categoryNoQuery string parameter — filter results by category
filters__makeNoQuery string parameter — filter results by make
filters__modelNoQuery string parameter — filter results by model
filters__type_idsNoQuery string parameter — filter results by type ids
filters__category_idsNoQuery string parameter — category filter by Ids
filters__make_idsNoQuery string parameter — filter results by make ids
filters__model_idsNoQuery string parameter — filter results by model ids
filters__yearNoQuery string parameter — filter results by year
filters__statusNoQuery string parameter — filter results by status
filters__ownershipNoQuery string parameter — filter results by ownership
filters__vendor_idsNoQuery string parameter — filter results by vendor ids
filters__group_idsNoQuery string parameter — filter results by group ids
filters__is_current_projectNoQuery string parameter — flag to filter by current project
filters__assignee_idsNoQuery string parameter — filter results by assignee ids
filters__updated_atNoQuery string parameter — updated at filter (date range format: YYYY-MM-DD...YYYY-MM-DD or YYYY-MM-DDTHH:MM:SSZ...YYYY-MM-DDTHH:MM:SSZ)
pageNoQuery string parameter — the page number to retrieve. Default is 1.
per_pageYesQuery string parameter — number of records per page
viewNoQuery string parameter — response detail level. Use 'normal' for standard fields or 'extended' for all fields
sortNoQuery string parameter — equipment sort. Also supports custom field sorting like 'custom_field_123' or '-custom_field_123' for descending
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds context: it is a GET request returning paginated JSON, and discloses the exact endpoint. There is no contradiction with 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?

The description is concise (3-4 sentences) and includes key information: purpose, usage, required params, pagination, API details. Every sentence contributes value, though it could be slightly more structured.

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 25 parameters and no output schema, the description provides adequate context (endpoint, pagination, required params) but could offer a summary of common filters or response structure. The schema descriptions fill the gaps, so it is adequate but not comprehensive.

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 has 100% parameter description coverage, so baseline is 3. The description adds value by highlighting required parameters and pagination control, but does not elaborate on the numerous filter parameters, which would be helpful.

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 the verb 'fetch' and the resource 'Equipment records' by project. It mentions pagination and required parameters. However, it says 'a specific Equipment records' which slightly contradicts the fact that it returns a list, causing minor confusion.

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 indicates when to use the tool (fetch equipment by project) but does not explicitly state when not to use it or mention alternative tools like 'get_equipment_by_id_project' for a single equipment.

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