Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show An Equipment Type

show_an_equipment_type
Read-onlyIdempotent

Retrieve detailed information about a specific equipment type using its ID and company ID. Returns JSON with full Field Productivity records.

Instructions

Return detailed information about a specific equipment type. Use this to fetch the full details of a specific Field Productivity records by its identifier. Returns a JSON object describing the requested Field Productivity records. Required parameters: id, company_id. Procore API: Project Management > Field Productivity. Endpoint: GET /rest/v1.0/companies/{company_id}/managed_equipment_types/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the company to get the types for
company_idYesURL path parameter — unique identifier for the company.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds 'Returns a JSON object' but no additional behavioral traits beyond 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?

Two sentences plus endpoint detail. Purpose front-loaded, no redundancy. Slightly verbose with 'Field Productivity records' repeated but overall efficient.

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 no output schema, description adequately states it returns a JSON object. Mentions required parameters and endpoint. Could specify return fields, but sufficient for a show operation.

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% with descriptions for all 4 parameters. Description only restates required parameters. Minimal added value beyond schema.

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?

Description clearly states the action ('Return detailed information') and resource ('specific equipment type'), distinguishing it from sibling tools like 'list_all_equipment_types' or 'create_an_equipment_type'. References 'Field Productivity records' for context.

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?

Explicitly instructs to use for fetching full details of a specific record by identifier. Lists required parameters. Does not mention when to avoid or provide alternatives, but context is clear.

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