Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Create Specification Section For A Project

create_specification_section_for_a_project

Create a new specification section in a Procore project by providing the project ID, section number, and division ID.

Instructions

Create Specification Section 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: project_id, number, specification_section_division_id. Procore API: Project Management > Specifications. Endpoint: POST /rest/v1.0/specification_sections

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesQuery string parameter — unique identifier for the project.
numberYesJSON request body field — the number for this Specifications operation
descriptionNoJSON request body field — the description for this Specifications operation
specification_section_division_idYesJSON request body field — the ID of the parent Specification Section Division

Tool Definition Quality

B3.2/5.0
Behavior3/5

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

Annotations already indicate write, non-destructive, non-idempotent behavior. Description adds return value (created object) and endpoint, but no additional behavioral traits beyond annotations.

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?

Description is concise, front-loaded, and includes essential info (required params, endpoint). However, it repeats tool name and has minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has 4 params, no output schema. Description mentions return value and endpoint, but lacks prerequisites, error handling, or explanation of what a specification section is. Adequate but not comprehensive.

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. Description mentions required parameters but adds no meaning beyond the schema's descriptions.

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?

Description clearly states it creates a specification section for a project, with required parameters. However, it uses 'Specifications' ambiguously and does not differentiate from sibling tools like create_specification_section_division_for_a_project.

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?

Description says 'Use this to create a new Specifications' but provides no guidance on when to use this tool vs alternatives, nor any prerequisites or exclusions.

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