Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Resource

show_resource_v1_0
Read-onlyIdempotent

Retrieve full details of a specific Schedule (Legacy) resource using its ID and project ID.

Instructions

Show detail on the specified Resource. Use this to fetch the full details of a specific Schedule (Legacy) records by its identifier. Returns a JSON object describing the requested Schedule (Legacy) records. Required parameters: id, project_id. Procore API: Project Management > Schedule (Legacy). Endpoint: GET /rest/v1.0/resources/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Schedule (Legacy) resource
project_idYesQuery string parameter — unique identifier for the project.
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 provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and description adds endpoint and return type. Description adds some context but does not go 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.

Conciseness5/5

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

Two sentences plus additional context (required params, API endpoint). Front-loaded with purpose, no wasted words.

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?

No output schema, but description states return type ('JSON object describing the requested Schedule (Legacy) records'). For a simple show tool with good annotations, this is complete enough.

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. Description mentions required parameters but adds no additional meaning beyond what schema provides.

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?

Clearly states the verb ('Show'/'fetch') and resource ('Resource'/'Schedule (Legacy) records'). Distinguishes from siblings like list_resources_v1_0 by specifying 'specific Resource' and 'by its identifier'.

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 says when to use: 'fetch the full details of a specific Schedule (Legacy) records by its identifier'. Does not mention when not to use or alternatives, but context of siblings implies alternatives.

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