Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get All Equipment Ids (Company)

get_all_equipment_ids_company
Read-onlyIdempotent

Retrieve a paginated list of all equipment IDs for a company. Apply filters by type, category, make, model, year, status, and more.

Instructions

Get all equipment ids (Company). 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: per_page, company_id. Procore API (v2.1): Core > Equipment. Endpoint: GET /rest/v2.1/companies/{company_id}/equipment_register/ids

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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__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 — status filter by ids
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__assignee_idsNoQuery string parameter — filter results by assignee ids
filters__current_project_idsNoQuery string parameter — current project filter by ids
filters__is_deletedNoQuery string parameter — filter results by is deleted
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
sortNoQuery string parameter — equipment sort. Also supports custom field sorting like 'custom_field_123' or '-custom_field_123' for descending
Behavior3/5

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

Annotations indicate read-only and idempotent behavior. The description adds pagination metadata detail but includes an inaccurate claim about fetching full details. This adds some value beyond annotations but is partially misleading, warranting a 3.

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 relatively concise but includes a contradictory and potentially misleading sentence. It could be shorter and more accurate. Structurally, it front-loads the main purpose but then detracts, resulting in a 3.

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?

Despite high parameter count and no output schema, the description fails to explain the response structure beyond 'paginated JSON array', and does not clarify that only IDs (not full records) are returned. Missing essential context for correct usage, hence a 2.

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 baseline is 3. The description only mentions page and per_page without adding new meaning. No additional value over schema descriptions, hence a 3.

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

Purpose3/5

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

The description states it retrieves all equipment IDs, which matches the title, but includes a contradictory sentence about fetching full details of a specific equipment record. This mixed messaging reduces clarity, earning a 3.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It only mentions pagination control and required parameters, but lacks context on selecting this tool over siblings. Score reflects minimal usage direction.

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