Skip to main content
Glama
TylerIlunga

Procore MCP Server

Show Incident Severity Level

show_incident_severity_level
Read-onlyIdempotent

Retrieve full details of a specific incident severity level using its ID and company ID. Returns a JSON object with complete severity level data.

Instructions

Returns the specified Incident Severity Level. Use this to fetch the full details of a specific Incidents by its identifier. Returns a JSON object describing the requested Incidents. Required parameters: company_id, id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/companies/{company_id}/incidents/severity_levels/{id}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
idYesURL path parameter — incident Severity Level ID
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior3/5

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

Annotations already declare readOnlyHint=true. Description adds no behavioral details beyond restating generic behavior. Lacks disclosure of pagination parameter effects.

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?

Two short sentences with endpoint info. Purpose is front-loaded. Could omit Procore API metadata for brevity, but still efficient.

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?

For a simple read operation with annotations covering safety, description covers purpose, required params, endpoint, and return type. Pagination param existence is not explained but acceptable.

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 repeats required params already in schema, adding no new meaning about their values or constraints.

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?

Description clearly states it returns a specified incident severity level and fetches full details by identifier. Differentiates from list or update operations by emphasizing specificity and single fetch.

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?

Implies singular use but does not explicitly state when to use versus listing or updating severity levels. No guidance on when not to use or alternatives.

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