Skip to main content
Glama
TylerIlunga

Procore MCP Server

Create Equipment Category (Project)

create_equipment_category_project

Add a new equipment category to a Procore project. Provide project ID, company ID, category name, and active status to create the record.

Instructions

Create equipment category (Project). Use this to create a new Equipment records in Procore. Creates a new Equipment records and returns the created object on success (HTTP 201). Required parameters: project_id, company_id, name, is_active. Procore API (v2.0): Core > Equipment. Endpoint: POST /rest/v2.0/companies/{company_id}/projects/{project_id}/equipment_register_categories

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
company_idYesURL path parameter — unique identifier for the company.
nameYesJSON request body field — the name of the equipment category.
is_activeYesJSON request body field — active/Inactive indicator for Equipment Category.
Behavior4/5

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

Annotations already indicate the tool is not read-only, not destructive, and idempotent. The description adds the HTTP status (201) and endpoint details, which provide additional behavioral context without contradicting annotations.

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?

The description is three sentences: purpose, success response, and required parameters with API endpoint. It is front-loaded with key information and contains no redundant content.

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?

No output schema, but the description mentions the created object is returned on success. Required parameters are listed. For a create tool with simple requirements, it is fairly complete, though it lacks error handling or prerequisite notes.

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?

Input schema covers all 4 parameters (100% coverage), so baseline is 3. The description adds value by specifying which parameters are path vs. body parameters and listing required fields, clarifying their roles beyond schema names.

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 verb 'create', the resource 'equipment category', and the scope 'Project'. It distinguishes itself from sibling tools like 'create_equipment_category_company' by including '(Project)' in the title and description.

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

Usage Guidelines3/5

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

The description does not provide explicit guidance on when to use this tool versus alternatives. It mentions required parameters but lacks context about prerequisites or scenarios for use.

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