Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Total Workers And Man Hours

get_total_workers_and_man_hours
Read-onlyIdempotent

Get total workers and man hours for a project between specified dates. Provide start and end dates to retrieve aggregated daily totals from the manpower log.

Instructions

Returns total workers and man hours between a start date and end date. To get a single day, supply the same date for start and end. Use this to fetch the full details of a specific Daily Log records by its identifier. Returns a paginated JSON array of Daily Log records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Project Management > Daily Log. Endpoint: GET /rest/v1.0/projects/{project_id}/manpower_logs/daily_totals

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
start_dateNoQuery string parameter — start date of specific logs desired in YYYY-MM-DD format (use together with end_date)
end_dateNoQuery string parameter — end date of specific logs desired in YYYY-MM-DD format (use together with start_date)
filters__created_by_idNoQuery string parameter — returns item(s) created by the specified User IDs.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior2/5

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

Annotations indicate readOnlyHint=true, which matches the read nature. However, the description includes contradictory statements about returning totals versus a paginated array of records. It mentions pagination but does not clarify the exact output format or that it aggregates data. This reduces transparency.

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

Conciseness2/5

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

The description is relatively short but contains redundant and contradictory information. It mixes purpose, endpoint details, and a confusing instruction. The structure is not clear; it front-loads the main action but then adds conflicting details.

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

Completeness1/5

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

The description is incomplete and confusing. It claims to return 'total workers and man hours' but also says it returns a 'paginated JSON array of Daily Log records'. Without an output schema, the agent cannot determine the actual response shape. Pagination metadata is mentioned but not specified. The description fails to provide a coherent picture.

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 the schema already documents parameters. The description adds a useful hint: 'To get a single day, supply the same date for start and end.' This is a small but clear addition. No further parameter details beyond the schema.

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 states 'Returns total workers and man hours' but later contradicts with 'Returns a paginated JSON array of Daily Log records' and 'fetch full details of a specific Daily Log records by its identifier'. This inconsistency obscures the true purpose and may mislead the agent.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description contains a confusing instruction about fetching 'full details of a specific Daily Log records', which does not align with the tool name or the rest of the description. Sibling tools include many similar list/show tools, but no differentiation is provided.

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