Skip to main content
Glama
Sign In
Corbel

Corbel

by sgoettl17
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Read from Procore

corbel_get
Read-only

Calls read-only Procore REST API GET endpoints to fetch records, using operation_id and optional pagination (all_pages, max_pages) for list results.

Instructions

Call a read-only (GET) endpoint of the Procore REST API (https://developers.procore.com/reference/rest/docs/rest-api-overview). Set all_pages to follow page/per_page pagination for list endpoints.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "operation_id": "<operation_id>"
    },
    "name": "corbel_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoQuery parameters. Nested objects become filters[key]=value; lists become key[]=value.
all_pagesNo
max_pagesNo
company_idNoOverride the configured Procore-Company-Id for this call.
path_paramsNoValues for the {placeholders} in the endpoint path, e.g. project_id.
operation_idYesoperation_id from corbel_search_endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

The readOnlyHint=true annotation already covers the safety profile, and the description is consistent with it by stating read-only GET. It adds pagination behavior via all_pages, but says nothing about auth requirements (the company_id override), the max_pages=10 cap, rate limits, or error/response shape for a generic passthrough tool.

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?

Two tight sentences with the core action front-loaded and the pagination hint appended; no filler. The inline URL consumes space but earns it by pointing to the endpoint catalogue.

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?

For a generic REST passthrough with six parameters and no output schema, the description covers the verb, safety, and pagination, but omits response shape, error behavior, and the discovery workflow needed to supply operation_id. Adequate but with visible gaps.

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 67%; all_pages and max_pages lack schema descriptions. The description compensates by explaining all_pages ('follow page/per_page pagination for list endpoints') but never mentions max_pages or its 1-10 bound, so one undocumented parameter remains unexplained beyond the schema.

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?

States a specific verb and resource: call a read-only GET endpoint of the Procore REST API, with a link to the API reference. It is clearly distinguishable from corbel_search_endpoints and corbel_describe_endpoint, which are discovery operations, though the description never names those siblings explicitly.

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?

It implies usage conditions: a GET, read-only call, with all_pages set for list endpoints. It does not state the prerequisite workflow (obtain operation_id via corbel_search_endpoints, inspect shape via corbel_describe_endpoint) or when not to use it, leaving that to inference from the schema and sibling names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools