Skip to main content
Glama
TylerIlunga

Procore MCP Server

Get Company Snapshots Summary

get_company_snapshots_summary
Read-onlyIdempotent

Retrieve a paginated summary of budget snapshots for a company by budget view ID. Filter by project, status, program, region, stage, office, department, creator, or date range.

Instructions

Returns a summary of all selected snapshots for a company. Use this to fetch the full details of a specific Budget records by its identifier. Returns a paginated JSON array of Budget records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id, budget_view_id. Procore API (v2.0): Construction Financials > Budget. Endpoint: GET /rest/v2.0/companies/{company_id}/budget_views/{budget_view_id}/project_status_snapshots/summary

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
budget_view_idYesURL path parameter — iD of the budget view
filters__status_idNoQuery string parameter — filter snapshots by PSS custom status ID
filters__project_idNoQuery string parameter — filter snapshots by project ID
filters__program_idNoQuery string parameter — filter snapshots by program ID
filters__region_idNoQuery string parameter — filter snapshots by region ID
filters__stage_idNoQuery string parameter — filter snapshots by stage ID
filters__office_idNoQuery string parameter — filter snapshots by office ID
filters__department_idNoQuery string parameter — filter snapshots by department ID
filters__created_by_idNoQuery string parameter — filter snapshots by created_by_id
filters__created_atNoQuery string parameter — filter snapshots by created_at date range, inclusive
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 indicate readOnlyHint=true and idempotentHint=true. The description adds that the response is paginated and includes metadata, which is useful but minimal. No discussion of permissions or other behavioral aspects. With annotations covering the safety profile, the description adds modest value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description contains a contradictory sentence that wastes space and confuses the purpose. While it front-loads the main action, the inclusion of API details (endpoint, version) is useful but the conflicting guidance makes it less concise and structured.

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?

Given the tool has 13 parameters, no output schema, and is a read operation, the description partially covers pagination and required params but fails to clarify the contradictory intent. The lack of output schema explanation and the confusing second sentence leave the description incomplete for an agent to fully understand the tool.

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?

The input schema has 100% coverage with descriptions for all 13 parameters. The description mentions required parameters and pagination controls but does not explain filter parameters beyond what the schema already provides. The description adds no extra meaning, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it returns a summary of selected snapshots for a company, but the second sentence about fetching full details of a specific Budget record contradicts this. The endpoint and purpose are partially clear, but the conflicting guidance reduces clarity.

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?

The description provides a misleading usage suggestion (fetch full details of a specific Budget record) and does not offer guidance on when to use this tool versus sibling tools like list_budget_view_snapshots or list_budget_view_snapshot_summary_rows. Pagination controls are mentioned, but no exclusions 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