Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Equipment Maintenance Log

update_equipment_maintenance_log

Update an existing equipment maintenance log by supplying only the fields that need to change, such as service dates or attachments. Returns the updated log object.

Instructions

Update a specified equipment maintenance log. Use this to update an existing Field Productivity records (only the supplied fields are changed). Updates the specified Field Productivity records and returns the modified object on success. Required parameters: id, company_id. Procore API: Project Management > Field Productivity. Endpoint: PATCH /rest/v1.0/companies/{company_id}/managed_equipment_maintenance_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — iD of the company to get the makes for
company_idYesURL path parameter — unique identifier for the company.
managed_equipment_idNoJSON request body field — equipment Id the maintenance log is associated with
last_service_dateNoJSON request body field — the Date the equipment was last services
next_service_dateNoJSON request body field — next service date for the equipment
upload_idsNoJSON request body field — the specified array of upload ids is saved as Managed Equipment Maintenance Logs Attachments.
Behavior3/5

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

Annotations already indicate mutation. Description adds that it returns modified object, but no further behavioral context like authorization or error handling.

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?

Three sentences, front-loaded, includes endpoint info but not essential. Reasonably concise.

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?

Covers basic operation and return value but lacks error handling, prerequisites, or output details. No output schema to compensate.

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 100% with parameter descriptions. Description only lists required params, adds no extra meaning beyond schema.

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 'Update a specified equipment maintenance log' with specific verb and resource. Minor confusion with 'Field Productivity records' but still clear.

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 explicit when-to-use or alternatives. Does not mention create vs update or other sibling tools.

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