Skip to main content
Glama
Procore MCP Server

Procore MCP Server

Discover Procore API Categories

procore_discover_categories
Read-onlyIdempotent

Browse Procore's API as a Category > Module tree with endpoint counts to find where your data lives. Starts the discover-detail-call workflow using exact names for subsequent endpoint lookup.

Instructions

Lists Procore's API surface as a Category > Module tree with an endpoint count for each. Start here when you do not yet know which part of Procore holds the data you need; if you already know the resource by name ('RFI', 'budget'), procore_search_endpoints gets you there in one step instead of three. The category and module names returned are the exact values procore_discover_endpoints expects. Takes no arguments and returns a JSON object. Reads the catalog bundled with this server, so it makes no Procore request and needs no authentication — it cannot fail with 401/403 and costs no rate limit. Step 1 of the discover -> detail -> call workflow.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "procore_discover_categories"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

The annotations already declare readOnly, idempotent, and non-destructive. The description adds significant behavioral context beyond those hints: it makes no Procore request, needs no authentication, cannot fail with 401/403, costs no rate limit, and returns a JSON object. It also connects the returned values to the expected inputs of procore_discover_endpoints, providing useful workflow behavior.

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

Conciseness5/5

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

Every sentence carries distinct value: the product description, when to use, the alternative tool, the output contract, the no-network behavior, and the workflow position. The content is front-loaded with the core purpose and then narrows to operational details, without repetition or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a zero-parameter tool with no output schema, the description covers the complete context an agent needs: what is returned, how the output is used downstream, that authentication is unnecessary, and which sibling tool to use instead. It fully satisfies the discover -> detail -> call workflow, leaving no ambiguity about its role.

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?

The input schema has zero parameters, so schema coverage is complete by default. The description confirms this with 'Takes no arguments', and adds clarity about the plain JSON object return, though it could have been slightly more explicit about this being an empty input contract. Otherwise, no parameter information is missing.

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 opens with a specific verb and resource: 'Lists Procore's API surface as a Category > Module tree with an endpoint count.' It clearly distinguishes itself as the first step of a discovery workflow and explicitly differentiates from procore_search_endpoints, which is an alternative for when the resource name is already known.

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

Usage Guidelines5/5

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

The description gives direct usage criteria: 'Start here when you do not yet know which part of Procore holds the data you need' and names the alternative when you do know the resource ('procore_search_endpoints gets you there in one step'). It also states it reads a bundled catalog, so it needs no authentication and costs no rate limit, which clarifies when to select it over network-calling tools.

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