Skip to main content
Glama
TylerIlunga

Procore MCP Server

list_waste_logs

Retrieve waste logs for construction projects to track material disposal and manage environmental compliance through the Procore API.

Instructions

List Waste Logs. [Project Management/Daily Log] GET /rest/v1.0/projects/{project_id}/waste_logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
log_dateNoDate of specific logs desired in YYYY-MM-DD format
start_dateNoStart date of specific logs desired in YYYY-MM-DD format (use together with end_date)
end_dateNoEnd date of specific logs desired in YYYY-MM-DD format (use together with start_date)
filters__created_by_idNoReturns item(s) created by the specified User IDs.
filters__vendor_idNoReturn item(s) with the specified Vendor IDs.
pageNoPage
per_pageNoElements per page
filters__daily_log_segment_idNoDaily Log Segment ID filter
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the action ('List Waste Logs') and includes an HTTP method hint ('GET'), but fails to describe critical behaviors like pagination, rate limits, authentication requirements, or what the response format looks like. This is inadequate for a tool with 9 parameters.

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?

The description is extremely concise with only one sentence and a technical endpoint reference. It is front-loaded and wastes no words, though it could benefit from more informative content. The structure is clear but minimal.

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?

Given the complexity (9 parameters, no annotations, no output schema), the description is incomplete. It does not explain the return values, pagination behavior, or any operational constraints. The agent lacks sufficient context to use this tool effectively beyond the basic schema.

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 description coverage is 100%, with each parameter well-documented in the input schema. The description adds no additional parameter semantics beyond what the schema provides, but the schema is comprehensive, so a baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List Waste Logs' is a tautology that restates the tool name with minimal additional information. It lacks specificity about what 'waste logs' are or what the listing operation entails, and does not distinguish this tool from sibling tools in the server.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, context, or any sibling tools that might serve similar purposes, leaving the agent with no usage direction.

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