Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Project Configurable Field Sets

list_project_configurable_field_sets
Read-onlyIdempotent

Enumerate project custom configurable tools by listing paginated configurable field sets. Filter by type, tool ID, or category.

Instructions

Return a list of all Configurable Field Sets associated with a Project. Use this to enumerate Custom - Configurable Tools when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Custom - Configurable Tools. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: project_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/projects/{project_id}/configurable_field_sets

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)
include_lov_entriesNoQuery string parameter — whether or not to include LOV entries in the response (defaults to true)
types__NoQuery string parameter — filter by of configurable field set types
include_default_configurable_field_setsNoQuery string parameter — flag to include the default values for each type of Configurable Field Set if one has not been created.
generic_tool_idNoQuery string parameter — filter by generic tool id(s). Could be a integer or an array of integer.
action_plan_type_idNoQuery string parameter — filter by Action Plan type id.
inspection_type_idNoQuery string parameter — filter by inspection type id.
observations_category_idNoQuery string parameter — filter by observations category id.
categoryNoQuery string parameter — filter by category.
Behavior4/5

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

Annotations already include readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds context about paginated JSON array return and pagination metadata. No contradictions with annotations.

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?

The description is three sentences, front-loaded with purpose and usage context. Every sentence adds value with no redundant or extraneous information.

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

Completeness3/5

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

Given 11 parameters and no output schema, the description covers basic purpose and pagination but lacks detail on the return structure beyond 'paginated JSON array'. The schema compensates for parameter descriptions, but the lack of output schema means the description could have provided more clarity on the response format.

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 11 parameters. The description mentions project_id as required and page/per_page for pagination, but does not add significant meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 a list of Configurable Field Sets for a Project, specifying it enumerates Custom - Configurable Tools with pagination and filtering options. It is distinct from sibling list tools by focusing on a specific resource type.

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 says when to use the tool (e.g., for paginated overview, finding IDs, filtering). It mentions pagination parameters and required project_id. However, it does not explicitly state when not to use it or list alternatives, leaving some ambiguity.

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