Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create Specification Section Division For A Project

create_specification_section_division_for_a_project

Create a specification section division for a Procore project. Supply a number and description to add new specifications.

Instructions

Create Specification Section Division for a Project. Use this to create a new Specifications in Procore. Creates a new Specifications and returns the created object on success (HTTP 201). Required parameters: number, description. Procore API: Project Management > Specifications. Endpoint: POST /rest/v1.0/specification_section_divisions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoQuery string parameter — unique identifier for the project.
numberYesJSON request body field — the number for this Specifications operation
descriptionYesJSON request body field — the description for this Specifications operation

Tool Definition Quality

C2.8/5.0
Behavior2/5

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and the description confirms it creates a resource. However, no additional behaviors are disclosed beyond the basic create action.

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?

Contains some redundancy between the first two sentences. Could be more concise while still providing endpoint info. Front-loading is adequate.

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?

Does not explain what a specification section division is, its relationship to other specification entities, or what the created object contains. No output schema present to supplement.

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 3. The description only repeats the required parameters without adding contextual meaning or clarifying the project_id parameter.

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 it creates a specification section division, but the phrase 'create a new Specifications' is ambiguous and might be confused with creating a full specification document rather than a division.

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 like create_specification_section or create_specification_area. Does not specify any conditions or 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