Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Witness Statement

create_witness_statement

Create a witness statement for a Procore incident, recording the witness's account with supporting files and details.

Instructions

Create Witness Statement. Use this to create a new Incidents in Procore. Creates a new Incidents and returns the created object on success (HTTP 201). Required parameters: project_id, incident_id, witness_id. Procore API: Project Management > Incidents. Endpoint: POST /rest/v1.0/projects/{project_id}/incidents/witness_statements

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
incident_idYesJSON request body field — the ID of the Incident
statementNoJSON request body field — the account of the event by the witness in rich text form.
date_receivedNoJSON request body field — date that the Witness Statement was received. This assumes the dates provided are in the project timezone.
witness_idYesJSON request body field — unique identifier of the witness
upload_uuidsNoJSON request body field — array of uploaded file UUIDs.
drawing_revision_idsNoJSON request body field — drawing Revisions to attach to the response
file_version_idsNoJSON request body field — file Versions to attach to the response
form_idsNoJSON request body field — forms to attach to the response
image_idsNoJSON request body field — images to attach to the response
custom_field_%{custom_field_definition_id}NoJSON request body field — value of the custom field. The data type of the value passed in corresponds with the data_type of the Custom Field Definition. For a lov_entry data_type the value passed in should be the ID of one ...
recordingNoJSON request body field — the recording for this Incidents operation
Behavior2/5

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

Annotations already indicate non-readOnly, non-destructive, non-idempotent. The description adds the response code (HTTP 201) but fails to disclose side effects, authorization needs, or error handling. Minimal behavioral insight.

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

Conciseness3/5

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

The description is short but contains redundancy ('Create Witness Statement' repeats the title) and awkward phrasing ('create a new Incidents'). Adequate but could be more concise and polished.

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 12 parameters, nested objects, no output schema, the description lacks guidance on complex fields (upload_uuids, drawing_revision_ids, etc.). It covers only the basic required parameters, leaving the agent underinformed.

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%, so baseline is 3. The description lists required parameters but does not add meaning beyond the schema. No additional semantic guidance for optional parameters like upload_uuids or custom fields.

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?

The description states the tool creates a witness statement and mentions required parameters. However, it repeats 'Incidents' oddly and does not explicitly differentiate from similar tools like 'update_witness_statement' or 'list_witness_statements'.

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 (e.g., update_witness_statement). It only says 'Use this to create a new Incidents' without explaining when not to use it or providing context on prerequisites.

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