Skip to main content
Glama
TylerIlunga

Procore MCP Server

Close And Distribute A Submittal Log

close_and_distribute_a_submittal_log
Idempotent

Close a submittal log and distribute it to specified recipients. Set the closed status, add a message, and notify selected users.

Instructions

Close and Distribute the specified Submittal Log. Send only the fields you intend to change; omitted fields keep their current values. 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 the modified and distribute a submittal log on success. 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 > Submittals. Endpoint: PATCH /rest/v1.0/projects/{project_id}/submittal_logs/{id}/close_and_distribute

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Submittals resource
messageNoJSON request body field — the message for this Submittals operation
project_idYesURL path parameter — unique identifier for the project.
recipient_idsNoJSON request body field — loginInformation IDs of users to be notified of the distribution. Available from `GET /rest/v1.0/projects/{project_id}/users`.
prostore_file_idsNoJSON request body field — prostore File IDs to attach directly to the distribution (e.g., new files uploaded as part of the distribution message).
selected_approversNoJSON request body field — the selected approvers for this Submittals operation
submittal_descriptionNoJSON request body field — submittal_description
submittal_log_status_idNoJSON request body field — the ID of a Submittal Status (from `GET /rest/v1.0/companies/{company_id}/submittal_statuses`) whose `status` is `Closed`. The Submittal Log will be transitioned to this status as part of the call.
submittal_attachment_idsNoJSON request body field — submittalAssociatedAttachment IDs to include in the distribution. IDs are resolved by `SubmittalAssociatedAttachment.id`. Available from `GET /rest/v1.0/projects/{project_id}/submittal_logs/{id}`.
Behavior4/5

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

Beyond annotations, the description explains PATCH semantics ('omitted fields keep their current values'), project_id defaulting, and common HTTP error statuses. The return value sentence is garbled, slightly reducing transparency, but the overall behavioral context is strong.

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 information-dense and front-loaded with the core purpose, but includes a grammatically broken return statement and some redundancy (endpoint, API section). Still, most sentences earn their place.

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

Completeness4/5

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

The description covers endpoint, required params, defaults, error handling, and the success return, though the return statement is unclear. Given the tool's complexity and the lack of an output schema, this is reasonably complete.

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%, so parameters are well-documented already. The description adds extra meaning by highlighting required parameters, project_id's default behavior, and id resolution guidance, which goes beyond the schema.

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 'Close and Distribute the specified Submittal Log,' which clearly identifies the action and resource. The endpoint and API section further reinforce the tool's purpose, and the name itself is highly specific.

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 actionable usage guidance: resolve `id` with the matching list tool first, and `project_id` defaults from procore_set_config. It does not explicitly name alternative tools, but these prerequisites give clear context for when to use it.

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