Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Delay Logs

show_delay_logs
Read-onlyIdempotent

Retrieve a single delay log by ID and project ID to view its complete field set. Read-only operation that returns full details for an existing log.

Instructions

Returns single Delay Log. Use this when you already know which delay log you want and need its full field set. project_id defaults to the value set by procore_set_config when omitted, and id must identify an existing parent record — resolve it with the matching list tool first. Returns a single JSON object describing the delay log. 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: project_id, id. Procore API: Project Management > Daily Log. Endpoint: GET /rest/v1.0/projects/{project_id}/delay_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Daily Log resource
project_idYesURL path parameter — unique identifier for the project.
Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive; the description adds meaningful behavioral context: error payloads with 401/403/404, the read-only guarantee ('changes nothing'), project_id defaulting from config, and the prerequisite that id must reference an existing record.

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?

The description is compact and front-loaded, with six sentences that each add value: purpose, usage, parameter behavior, return type, error handling, and endpoint context. No redundancy 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?

For a simple 2-parameter read tool with no output schema, the description fully covers the return format ('single JSON object'), error semantics, prerequisites, and even the API endpoint. Nothing essential is missing.

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 covers both parameters fully (100%), but description adds useful semantics: project_id defaults from procore_set_config when omitted, and id must identify an existing parent record. However, the statement that project_id defaults when omitted conflicts with the schema marking it required, which could confuse an agent.

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?

Opens with 'Returns single Delay Log' — a specific verb+resource. The phrase 'Use this when you already know which delay log you want and need its full field set' clearly distinguishes it from list-style siblings and the get-by-id nature.

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?

Explicitly states when to use the tool ('when you already know which delay log you want') and directs the agent to the alternative ('resolve it with the matching list tool first'). This gives clear context for choosing this tool over list_delay_logs.

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