Skip to main content
Glama
TylerIlunga

Procore MCP Server

Validate Disbursement

validate_disbursement

Validate a disbursement before posting to ensure accuracy of payment details, including amount, payouts, and bank account information.

Instructions

Validates a disbursement before creation. Use this to perform the validate disbursement action on Payments. Creates a new Payments and returns the created object on success (HTTP 201). Required parameters: company_id, amount, payouts, workflowsConfigured, bankAccountId, bankAccountType. Procore API: Construction Financials > Payments. Endpoint: POST /rest/v1.0/companies/{company_id}/payments/disbursements/validate

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_idYesURL path parameter — unique identifier for the company.
amountYesJSON request body field — dollar amount of the disbursement times 100. Ex: $100.51 = 10051
payoutsYesJSON request body field — list of payouts in the disbursement. Each payout represents a payment to a business for an invoice.
workflowsConfiguredYesJSON request body field — whether workflows template is configured or not
nameNoJSON request body field — name of the disbursement
statusNoJSON request body field — status of the disbursement
bankAccountIdYesJSON request body field — uUID of the bank account
bankAccountTypeYesJSON request body field — type of the bank account
Behavior4/5

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

Description adds that it 'Creates a new Payments and returns the created object on success (HTTP 201)', which goes beyond annotations. However, it doesn't elaborate on failure scenarios or side effects implied by openWorldHint.

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?

Concise, front-loaded purpose, every sentence valuable. Includes endpoint and required params without redundancy.

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?

Adequately explains purpose and creation behavior, but lacks details on validation rules, error responses, and return object structure. With no output schema, description should cover return values more thoroughly.

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 baseline is 3. Description lists required parameters but adds no extra meaning beyond what the schema already provides.

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 'Validates a disbursement before creation' and specifies the action on Payments. It distinguishes from sibling 'validate_existing_disbursement' by focusing on pre-creation validation.

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?

Provides context ('before creation') and lists required parameters, but does not explicitly state when to avoid using this tool or when to use alternatives like 'validate_existing_disbursement'.

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