Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create A New Time And Material Entry

create_a_new_time_and_material_entry

Creates a new time and material entry for a project to record field productivity data. Requires project ID to submit work performed on a ticket.

Instructions

Create a new Time And Material Entry associated with the specified project. Use this to create a new Field Productivity records in Procore. Creates a new Field Productivity records and returns the created object on success (HTTP 201). Required parameters: project_id. Procore API: Project Management > Field Productivity. Endpoint: POST /rest/v1.0/projects/{project_id}/time_and_material_entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
run_configurable_validationsNoQuery string parameter — if true, validations are run for the corresponding Configurable Field Set.
nameNoJSON request body field — the title of T&M ticket
reference_numberNoJSON request body field — the refrence number associate with T&M ticket
descriptionNoJSON request body field — the description of job
statusNoJSON request body field — current status of T&M ticket
privateNoJSON request body field — if the T&M ticket is private
numberNoJSON request body field — unique number for the T&M ticket
customer_signature_idNoJSON request body field — the ID associate with customer's signature
company_signature_idNoJSON request body field — the ID associate with company's signature
company_signee_party_idNoJSON request body field — the ID associate with company's signature party
customer_signee_party_idNoJSON request body field — the ID associate with customer's signature party
work_performed_on_dateNoJSON request body field — date work performed on
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
file_version_idsNoJSON request body field — file Versions to attach to the response
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
upload_idsNoJSON request body field — the specified array of upload ids is saved as Time And Material Entry Attachments.
Behavior3/5

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

Annotations already indicate a write operation (readOnlyHint false, destructiveHint false). Description adds that it returns the created object on success (HTTP 201) and provides the endpoint, but lacks details on permissions, idempotency, or side effects. Adequate but not enhanced.

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?

Repetitive phrasing ('Create a new... Creates a new...') and includes redundant lines (Procore API, endpoint). Could be more concise by removing duplication while retaining essential info.

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

Completeness3/5

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

No output schema, but description mentions return value. Lacks context on validation (e.g., run_configurable_validations), dependencies, or typical usage patterns. Adequate for a basic create tool but incomplete for the 18 parameters.

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 baseline is 3. Description only mentions required parameter project_id, adding no explanation for the other 17 parameters. Does not compensate for schema coverage.

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

Purpose4/5

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

Clearly states verb 'create' and resource 'Time And Material Entry' associated with project. Mentions 'Field Productivity records' but does not explicitly differentiate from sibling tools like create_a_new_time_and_material_equipment_log. The name itself is unambiguous.

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. Only says 'Use this to create a new Field Productivity records' without exclusions or comparisons to similar create tools among the extensive sibling list.

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