Skip to main content
Glama
TylerIlunga

Procore MCP Server

Update Drawing Set

update_drawing_set

Update an existing drawing set's name or date. Modify only the supplied fields in a Procore project.

Instructions

Update an existing Drawing Set in the specified Project. Use this to update an existing Drawings (only the supplied fields are changed). Updates the specified Drawings and returns the modified object on success. Required parameters: project_id, id. Procore API: Project Management > Drawings. Endpoint: PATCH /rest/v1.0/projects/{project_id}/drawing_sets/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
idYesURL path parameter — iD of the drawing set
nameNoJSON request body field — drawing Set name
dateNoJSON request body field — drawing Set date
Behavior4/5

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

The description reveals partial update behavior and return of modified object, which goes beyond annotations. No contradiction with annotations (readOnlyHint=false, destructiveHint=false).

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?

Three sentences with no wasted words: purpose, usage guidance, and technical reference (required params, API endpoint). Front-loaded effectively.

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?

For a 4-parameter tool without output schema, the description covers partial update, required fields, and endpoint. All essential info is present and no gaps.

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 coverage is 100%, baseline 3. The description adds that only supplied fields are changed and identifies required parameters, clarifying the partial update semantics beyond schema descriptions.

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 clearly states the tool updates an existing Drawing Set, specifying 'only the supplied fields are changed' and that it returns the modified object. This distinguishes it from create or delete tools.

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 says 'Use this to update an existing Drawings' and lists required parameters, but does not explicitly state when not to use it or mention alternatives. Still, the context is clear.

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