Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Accident Logs

show_accident_logs
Read-onlyIdempotent

Retrieve a single accident log with its full set of fields by specifying project ID and log ID. Returns a JSON object from Procore's Daily Log without making changes.

Instructions

Returns single Accident Log. Use this when you already know which accident 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 accident 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}/accident_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.
Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive. Description adds valuable context about project_id defaulting to procore_set_config, id requiring an existing parent record, and detailed error payload behavior (401/403/404). This goes beyond the 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?

Every sentence carries purpose: purpose, usage criteria, defaults, return type, read-only note, error handling, required params, and API reference. No fluff; well-front-loaded and compact.

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?

Despite no output schema, the description covers return format, prerequisites, error cases, and API endpoint. For a single-record read tool, it is comprehensive and leaves no major gaps.

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 coverage is 100%, but the descriptions are minimal. The description adds meaning by explaining project_id omits to a default value and that id must be resolved beforehand, enriching the parameter understanding beyond the 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?

States 'Returns single Accident Log' with a specific verb and resource. Clearly distinguishes from list_accident_logs by noting this is for when you already know which log you want and need the full field set.

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 says 'Use this when you already know which accident log you want' and advises resolving the id with the matching list tool first. Also documents default behavior for project_id, providing clear when-to-use and alternative guidance.

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