Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Submittal

show_submittal_v1_0
Read-onlyIdempotent

Retrieve full details of a specific submittal using its unique identifier and project ID. Provides a JSON object with submittal information.

Instructions

This is a deprecated endpoint. Please use /submittals/{id} endpoint. Use this to fetch the full details of a specific Submittals by its identifier. Returns a JSON object describing the requested Submittals. Required parameters: id, project_id. Procore API: Project Management > Submittals. Endpoint: GET /rest/v1.0/submittal_logs/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesURL path parameter — unique identifier of the Submittals resource
project_idYesQuery string parameter — unique identifier for the project.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds deprecation status and endpoint path, enhancing transparency beyond annotations without contradiction.

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?

Four sentences cover deprecation, purpose, return type, required params, and API path, all relevant and front-loaded with the most critical information.

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 purpose, alternative, required params, and endpoint. However, does not address optional pagination parameters (page, per_page) which may be irrelevant for a single-resource endpoint, leaving slight ambiguity.

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 covers all parameters with descriptions (100% coverage), and the description only lists required parameters without adding new meaning. Baseline 3 applies.

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 fetches full details of a specific Submittal by identifier, with a deprecation warning that distinguishes it from siblings like show_submittal_project.

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 directs users to the newer /submittals/{id} endpoint, providing a clear alternative. Implies usage for fetching a single submittal's details, separating it from listing 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