Skip to main content
Glama
TylerIlunga

Procore MCP Server

List Tax Codes

list_tax_codes
Read-onlyIdempotent

Retrieve paginated list of tax codes for a company. Use to find tax code IDs and filter by query parameters.

Instructions

Return a list of all Tax Codes for a given Company When tax suport is enabled in Procore you can associate line items with a specific Tax Code. The Tax Code (sometimes known as a Tax Group) determines the tax rate to be applied to the line item for each Tax Type defined in Procore (Note that presently Procore only supports a single Tax Type per company). You may define as many Tax Codes as required. Through the web interface, a Procore admin user may identify one of these tax codes as the d... Use this to enumerate Tax records when you need a paginated overview, to find IDs, or to filter by query parameters. Returns a paginated JSON array of Tax records. Use page and per_page to control pagination; the response includes pagination metadata. Required parameters: company_id. Procore API: Construction Financials > Tax. Endpoint: GET /rest/v1.0/tax_codes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesQuery string parameter — unique identifier for the company.
pageNoQuery string parameter — page number for paginated results (default: 1)
per_pageNoQuery string parameter — expect number of items in response. min: 1, max: 100
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds valuable behavioral context: paginated JSON array response with pagination metadata, and the ability to control pagination via page and per_page. No contradiction 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.

Conciseness3/5

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

The description includes some background information (e.g., Tax Group terminology) that is not essential for an agent to use the tool. It could be more front-loaded and concise. Grammar issues like 'suport' also detract.

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 no output schema, the description adequately describes the response as a paginated JSON array with metadata. It also includes the API endpoint and required parameter. Some context about tax support could be assumed, but overall complete for a list 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?

Input schema has 100% parameter description coverage, so the description adds limited value. It mentions required parameter company_id and pagination parameters, which are already documented in the schema. Baseline is 3 given high schema coverage.

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 Tax Codes for a given company, with specific verbs like 'Return' and 'list', and identifies the resource (Tax Codes). It also mentions use cases like paginated overview, finding IDs, and filtering, making the purpose highly specific.

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 guidance on when to use the tool: to enumerate Tax records for paginated overview, find IDs, or filter by query parameters. However, it does not mention when not to use it or list alternative tools, which would improve the score.

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