Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Units Of Measure

list_units_of_measure
Read-onlyIdempotent

Retrieve a company's units of measure (UOMs), including standard and custom, to discover available units or look up a unit's ID for use in other calls.

Instructions

Returns the Units of Measure (UOMs) configured for the company, grouped by UOM Category. Includes both Procore-provided standard UOMs (those with is_standard: true, e.g., hours, sf) and any custom UOMs defined by the company. Pass view=ids_only to return only the IDs. Filter by filters[id] (single ID or array) and filters[updated_at] (ISO 8601 datetime range) to narrow the result set. Use this to discover units or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of units; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id. Procore API: Construction Financials > Units of Measure. Endpoint: GET /rest/v1.0/companies/{company_id}/uoms

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoQuery string parameter — page number for paginated results (default: 1)
viewNoQuery string parameter — serialization view. When set to `ids_only`, the response body is a JSON array of integer Unit of Measure IDs (pagination headers still apply). Omit for the default view (full UOM objects grouped by...
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesURL path parameter — unique identifier for the company.
filters__idNoQuery string parameter — restrict results to UOMs with one or more matching IDs. Example: `filters[id]=[101,102]`.
filters__updated_atNoQuery string parameter — return item(s) within a specific updated at iso8601 datetime range

Tool Definition Quality

A4/5.0
Behavior4/5

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

The description adds valuable context beyond annotations: it clarifies read-only behavior, error responses with common HTTP statuses, JSON array return, and pagination reporting. The annotations already declare safety, so this extra context earns a solid score.

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 thorough and well-organized, covering purpose, filters, use case, defaults, return format, errors, and API reference. While longer than strictly necessary, each sentence contributes useful information.

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 the absence of an output schema, the description covers return type, pagination, filters, error handling, and usage context. It could specify the exact structure of grouped UOMs, but overall it is sufficient for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds semantics for company_id defaulting to procore_set_config, the ids_only view, filter syntax, and pagination behavior. This goes beyond the bare schema descriptions.

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 tool returns the company's Units of Measure, grouped by category, and includes both standard and custom UOMs. However, it does not differentiate from the similarly-named sibling tool get_units_of_measure, so the distinction is not explicit.

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?

It explicitly states the use case of discovering units or looking up an id before calling another tool, and explains filtering and view options. It does not say when to avoid this tool in favor of get_units_of_measure, so alternatives are not fully covered.

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