Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show A Timesheet

show_a_timesheet
Read-onlyIdempotent

Fetch the full field set for an existing timesheet by project and timesheet ID. Read-only operation returns a single JSON object.

Instructions

Return Timesheet detailed information. Use this when you already know which timesheet 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 timesheet. 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 > Field Productivity. Endpoint: GET /rest/v1.0/projects/{project_id}/timesheets/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Field Productivity 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?

Beyond the readOnlyHint annotation, the description discloses meaningful behavioral traits: project_id defaulting to procore_set_config, the requirement for an existing parent id, return of a single JSON object, and specific error HTTP statuses (401, 403, 404). No contradiction with 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?

The description is dense but well-structured: purpose, usage, parameter defaults, return type, read-only note, error handling, required params, and API endpoint. Each sentence contributes; no 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?

With no output schema, the description appropriately explains the return value ('single JSON object') and error behavior. It also covers prerequisites, defaults, and endpoint info, making it complete for a read-only GET tool.

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 already covers both parameters at 100%, so baseline is 3. The description adds practical meaning: project_id falls back to procore_set_config when omitted, and id must resolve to an existing record. This enriches the schema's dry 'URL path parameter' labels.

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 opens with 'Return Timesheet detailed information,' a specific verb+resource statement. It further clarifies scope with 'need its full field set,' differentiating from list or mutation tools like list_all_timesheets or create_timesheet.

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

Usage Guidelines4/5

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

The description provides explicit usage context: 'Use this when you already know which timesheet you want.' It also instructs to resolve the id with the 'matching list tool first,' implying the list tool as an alternative. It lacks a named alternative or explicit when-not, so it stops short of a 5.

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