Skip to main content
Glama
TylerIlunga

Procore MCP Server

by TylerIlunga
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

List Filter Options For Submittal Manager

list_filter_options_for_submittal_manager
Read-onlyIdempotent

Retrieve available filter options for Submittal Manager in a Procore project to paginate and filter submittals by query parameters. Returns JSON array of filter values.

Instructions

Returns all Filter Options for Submittal Manager 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_manager_id

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesURL path parameter — unique identifier for the project.
pageNoQuery string parameter ��� page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)

Tool Definition Quality

A3.5/5.0
Behavior3/5

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

Annotations already cover readOnly, non-destructive, idempotent. Description adds endpoint and return type (JSON array), but does not significantly extend beyond annotations.

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 sentences plus endpoint info; efficient but includes redundant 'Required parameters: project_id' given schema. Minor waste but overall concise.

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 tool's simplicity, good annotations, and full schema coverage, the description covers return type and use cases adequately. No output schema needed.

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 parameters are fully described there. Description only mentions required project_id, adding no new meaning beyond schema.

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

Purpose4/5

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

Description clearly states 'Returns all Filter Options for Submittal Manager defined for the project.' and provides use cases. However, it does not explicitly differentiate from sibling filter option tools, relying on the tool name for specificity.

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?

Provides some guidance on when to use ('enumerate Submittals, find IDs, filter by query parameters') but lacks when-not-to-use or alternatives, which are numerous siblings.

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