Skip to main content
Glama
TylerIlunga

Procore MCP Server

create_timecard_entry_v1_1

Create timecard entries in Procore projects to track work hours, billable status, and labor details for accurate project management and payroll processing.

Instructions

Create Timecard Entry. [Project Management/Field Productivity] POST /rest/v1.1/projects/{project_id}/project_timecard_entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUnique identifier for the project.
hoursNoTotal number of hours worked (excluding breaks) for the timecard entry. This property is not required if the timesheet time entry is configured for start time and stop time.
lunch_timeNoThe duration of the lunch break, in minutes, for the Timecard Entry. This property is only required if the timesheet time entry is configured for start time and stop time.
time_inNoThe start time of the Timecard Entry in ISO 8601 format. This property is only required if the timesheet time entry is configured for start time and stop time.
time_outNoThe stop time of the Timecard Entry in ISO 8601 format. This property is only required if the timesheet time entry is configured for start time and stop time.
billableNoThe billable status of the Timecard Entry. Must be either true or false.
dateNoThe date of the Timecard Entry in ISO 8601 format.
descriptionNoThe description of the Timecard Entry.
timecard_time_type_idNoThe ID of the Timecard Time Type corresponding to the Timecard Entry property.
timesheet_idNoThe ID of the Timesheet corresponding to the Timecard Entry property.
cost_code_idNoThe ID of the Cost Code corresponding to the Timecard Entry property.
sub_job_idNoThe ID of the Subjob corresponding to the Timecard Entry property.
location_idNoThe ID of the Location corresponding to the Timecard Entry property.
login_information_idNoThe ID of the Login Information corresponding to the Timecard Entry property.
party_idNoThe ID of the Party corresponding to the Timecard Entry property.
origin_idNoThe ID of the related external data.
origin_dataNoThe value of the related external data.
line_item_type_idNoThe ID of the line item type corresponding to the time card entry.
custom_field_%{custom_field_definition_id}NoValue of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Create Timecard Entry' which implies a write operation, but does not disclose any behavioral traits such as required permissions, whether the operation is idempotent, what happens on failure, or any rate limits. The API endpoint hint ('POST') suggests a mutation, but this is insufficient for a tool with 19 parameters and no safety annotations.

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—just one sentence fragment plus an API endpoint. It is front-loaded with the core action ('Create Timecard Entry') and wastes no words. However, it is arguably too terse given the tool's complexity (19 parameters, no annotations), but within the bounds of efficient communication.

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 tool's high complexity (19 parameters, mutation operation, no annotations, no output schema), the description is inadequate. It does not explain the purpose beyond the name, offers no usage context, and provides minimal behavioral transparency. For a creation tool with many parameters and no structured safety hints, the description should do much more to guide the agent.

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%, meaning all 19 parameters are documented in the input schema with clear descriptions. The description adds no parameter-specific information beyond what the schema provides. According to the rules, when schema coverage is high (>80%), the baseline score is 3 even with no param info in the description. The description does not compensate or add value, but it also does not detract.

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 'Create Timecard Entry' is a tautology that restates the tool name without adding specificity. It includes a category tag '[Project Management/Field Productivity]' and an API endpoint 'POST /rest/v1.1/projects/{project_id}/project_timecard_entries', but these do not clarify what the tool actually does beyond the obvious 'create' action. It fails to distinguish this tool from sibling tools like 'create_timecard_entry_company' or 'create_timecard_entry_project'.

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 (e.g., 'create_timecard_entry_company' or 'create_timecard_entry_project') that might serve similar purposes. The agent is left with no usage instructions beyond the generic 'create' action.

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