Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Checklist Signature

create_checklist_signature

Creates a signature for a checklist signature request in Procore inspections. Requires list ID, signature request ID, project ID, and attachment.

Instructions

Creates a Signature for a specified Checklist Signature Request. Use this to create a new Inspections in Procore. Creates a new Inspections and returns the created object on success (HTTP 201). Required parameters: list_id, signature_request_id, project_id, attachment. Procore API: Project Management > Inspections. Endpoint: POST /rest/v1.0/checklist/lists/{list_id}/signature_requests/{signature_request_id}/signature

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesURL path parameter — unique identifier of the list
signature_request_idYesURL path parameter — checklist Signature Request ID
project_idYesQuery string parameter — unique identifier for the project.
attachmentYesJSON request body field — attachment representing the Signature. To upload an attachment you must upload the entire payload as `multipart/form-data` content-type and specify each parameter as form-data together with the `si...
attachment_stringNoJSON request body field — base64 encoded string representing PNG image of signature
Behavior3/5

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

The description provides the endpoint and HTTP 201 response code, adding some context beyond annotations. However, the confusing reference to inspections detracts from transparency. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is redundant and contains contradictory statements (e.g., multiple mentions of 'creates a new Inspections'). It is not efficiently structured and wastes words.

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?

With no output schema, the description should explain the response shape and the relationship between signature request and signature. The erroneous inspection text further reduces completeness.

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%, and the description only restates required parameters without adding meaning that the schema does not already provide. Baseline score of 3 applies.

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 states it creates a signature but then incorrectly says 'Use this to create a new Inspections in Procore' and repeats this, creating confusion about the actual purpose. It should clearly focus on signature creation.

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, such as the related create_checklist_signature_request or other inspection tools. The description does not help the agent distinguish between 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