Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Configurable Field Sets

list_configurable_field_sets
Read-onlyIdempotent

Retrieve a paginated list of all Configurable Field Sets for a company, with optional filters by type or tool ID.

Instructions

Return a list of all Configurable Field Sets associated with a Company. 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: company_id. Procore API: Company Admin > Custom - Configurable Tools. Endpoint: GET /rest/v1.0/companies/{company_id}/configurable_field_sets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
include_lov_entriesNoQuery string parameter — whether or not to include LOV entries in the response (defaults to true)
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — number of items per page (default: 100, max: 100)
filters__type__NoQuery string parameter — filter by field set type(s). Could be a string or an array of string.
filters__generic_tool_id__NoQuery string parameter — filter by generic tool id(s). Could be a integer or an array of integer.
viewNoQuery string parameter — specify which view to render. Options are common, extended, mobile, or with_project_ids
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive. The description adds context about paginated response, JSON array, and pagination metadata. No contradictions. No additional caveats like rate limits, but adequate.

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?

Description is three sentences plus endpoint reference, efficiently conveying purpose, usage, and key behavior without waste. Front-loaded with main action.

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?

For a 7-parameter paginated list tool, the description covers essential context: company scope, pagination, filtering, response format. No output schema, but mentions pagination metadata. Could detail response objects, but sufficient.

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?

Input schema has 100% description coverage with clear parameter descriptions. The description reinforces pagination controls and required company_id. Does not add significant meaning beyond schema, so 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 all Configurable Field Sets associated with a Company, using specific verbs and resource. It distinguishes from siblings like list_project_configurable_field_sets by specifying company-level scope.

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 provides explicit use cases: paginated overview, finding IDs, filtering. It mentions pagination controls. However, it does not explicitly contrast with sibling tools for project-level or single item retrieval.

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