Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Filter Options For Submittal Package

list_filter_options_for_submittal_package
Read-onlyIdempotent

Retrieve all filter options for submittal packages in a project to enumerate submittals, find IDs, or paginate through results.

Instructions

Returns all Filter Options for Submittal Package defined for the project. Use this to enumerate Submittals when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a JSON array of available filter values for Submittals. Required parameters: project_id. Procore API: Project Management > Submittals. Endpoint: GET /rest/v1.0/projects/{project_id}/submittals/filter_options/submittal_package_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
pageNoPage number for paginated results (default: 1)
per_pageNoNumber of items per page (default: 100, max: 100)
Behavior4/5

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

Annotations indicate the tool is read-only and idempotent, and the description adds that it returns a JSON array, consistent with the annotations. No contradictions.

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?

Four sentences, front-loaded with purpose, no redundant information.

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?

Given the absence of an output schema, the description could explain the returned values more precisely, but it covers the essential purpose, usage, and required parameter.

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 schema fully documents all parameters; the description only reiterates the required field and does not add further semantic detail beyond 'required parameters: project_id'.

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 tool returns filter options for submittal packages, specifies its use for enumerating submittals, and distinguishes itself from other filter option tools by focusing on submittal_package_id.

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 suggests using this tool to get filter options for paginated submittal overviews, finding IDs, or filtering by query parameters, but does not explicitly differentiate from other similar filter option tools.

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