Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Checklist Signature Request

create_checklist_signature_request

Create a checklist signature request by specifying list, project, and signatory IDs. Resolves the parent list and returns the new record with its ID.

Instructions

Creates a Signature Request for a specified Checklist. Pass the record's fields as top-level arguments — they are nested under "signature_request" in the request payload for you. list_id must identify an existing parent record — resolve it with the matching list tool first. Creates the checklist signature request and returns it with its new id (HTTP 201); calling it again creates another record. 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: list_id, project_id, signatory_id. Procore API: Project Management > Inspections. Endpoint: POST /rest/v1.0/checklist/lists/{list_id}/signature_requests

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesURL path parameter — unique identifier of the list
project_idYesQuery string parameter — unique identifier for the project.
signatory_idYesJSON request body field — iD of the User requested to sign
Behavior4/5

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

Annotations already indicate non-read-only and non-idempotent behavior. The description adds useful context about payload transformation and common error status codes (401, 403, 404), going beyond the structured annotation data.

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 dense and informative, with the main action front-loaded. It is slightly long but every sentence contributes meaningful details without unnecessary fluff.

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?

Covers creation, return of new ID, HTTP status, error cases, required parameters, and endpoint. Since there is no output schema, the description adequately explains the expected response behavior.

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 covers all 3 parameters with descriptions. The description adds value by explaining that top-level arguments map to a nested 'signature_request' payload and that list_id must reference an existing parent record.

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?

Clearly states 'Creates a Signature Request for a specified Checklist' with a specific verb and resource. It distinguishes from sibling tools like list_checklist_signature_requests and show_checklist_signature_request by the create action and includes the endpoint context.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to resolve list_id with the matching list tool first, provides context on payload nesting, and notes that calling it again creates another record, giving clear when/when-not guidance.

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