Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Harm Sources

list_harm_sources
Read-onlyIdempotent

Retrieve a paginated list of harm sources for a company to identify hazards. Use it to look up harm source IDs before reporting incidents.

Instructions

Returns a paginated list of harm sources for the specified company. Harm sources identify the material, substance, or object that caused or could cause harm in an incident. Use this to discover harm sources or to look up the id of one before calling a tool that needs it. company_id defaults to the value set by procore_set_config when omitted. Returns a JSON array of harm sources; page and per_page control pagination and the response reports how many pages remain. Read-only — it changes nothing in Procore. Failures come back as an error payload carrying the HTTP status — commonly 401 when the token has expired, 403 without tool permission, and 404 when an id does not resolve. Required parameters: company_id. Procore API: Project Management > Incidents. Endpoint: GET /rest/v1.0/companies/{company_id}/incidents/harm_sources

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoQuery string parameter — when true, returns both active and inactive harm sources. When omitted or false, returns only active harm sources.
pageNoQuery string parameter — page number for paginated results (default: 1)
sortNoQuery string parameter — sort direction. Use the value to sort ascending, or prefix with a hyphen (e.g. -name) to sort descending.
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
company_idYesURL path parameter — unique identifier for the company.
filters__idNoQuery string parameter — return item(s) with the specified IDs.
filters__activeNoQuery string parameter — if true, returns item(s) with a status of 'active'.
filters__updated_atNoQuery string parameter — return item(s) last updated within the specified ISO 8601 datetime range. Formats: `YYYY-MM-DD`...`YYYY-MM-DD` - Date `YYYY-MM-DDTHH:MM:SSZ`...`YYYY-MM-DDTHH:MM:SSZ` - DateTime with UTC Offset `YYY...
Behavior5/5

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

Beyond the read-only annotation, the description discloses pagination behavior, the default company_id from procore_set_config, the JSON array return format, and detailed error scenarios (401/403/404). This goes well beyond what annotations alone provide and helps the agent anticipate outcomes.

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?

Every sentence carries useful information: purpose, domain definition, usage, defaults, pagination, safety, error handling, required params, and API reference. It is front-loaded and has no filler.

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

Completeness5/5

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

Given the lack of an output schema, the description covers return type, pagination behavior, errors, and the required parameter. It is sufficiently complete for an agent to invoke the tool correctly without additional context.

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?

Schema coverage is 100%, but the description adds useful context: company_id defaults to the configured value, and page/per_page control pagination. It also flags company_id as required, reinforcing the schema.

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 first sentence clearly states the tool returns a paginated list of harm sources for a specified company. It defines what harm sources are and distinguishes this from related tools like show_harm_source and create_harm_source by focusing on listing and discovery.

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

Usage Guidelines4/5

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

The description explicitly advises using this tool to discover harm sources or look up an id before calling a tool that needs it. It does not name specific alternative tools or exclusions, but the intended use case is clear and practical.

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