Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Accident Logs

show_accident_logs
Read-onlyIdempotent

Retrieve the complete details of a specific accident log record using its project and log identifiers.

Instructions

Returns single Accident Log. Use this to fetch the full details of a specific Daily Log records by its identifier. Returns a JSON object describing the requested Daily Log records. 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
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — unique identifier of the Daily Log resource
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 declare readOnly and idempotent hints; the description adds no behavioral context beyond confirming a JSON output.

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

Conciseness3/5

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

The description contains redundancy ('Returns a JSON object' after stating 'Returns single Accident Log') and includes optional API info; could be more streamlined.

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

Completeness2/5

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

No output schema; description vaguely mentions 'Daily Log records' without specifying fields. Pagination parameters (page, per_page) are in schema but unmentioned, potentially confusing for a single-resource endpoint.

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% and description merely restates required params without providing additional semantics or clarifications.

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 clearly states the tool 'Returns single Accident Log' and that it fetches full details by identifier, distinguishing it from list functions.

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

Usage Guidelines3/5

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

It instructs to use with project_id and id, but does not explicitly compare to sibling list_accident_logs or exclude usage scenarios.

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