Skip to main content
Glama

Validate a batch of LATAM payout beneficiaries

validate_payout_batch
Read-onlyIdempotent

Validate up to 100 beneficiaries in one call (payroll runs, supplier files, marketplace withdrawals). Each item takes the same fields as validate_payout_beneficiary. Returns a summary count per verdict and per-item results.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>"
    },
    "name": "validate_payout_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description adds useful batch-specific context: the 100-item cap, the relationship to the single-beneficiary schema, and the shape of the returned summary and per-item results. It does not disclose verdict values or how partial failures are handled.

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 tight sentences: what it does, what input model it follows, and what it returns. It is front-loaded with the batch purpose and contains no redundant restatement of the title.

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 batch validation tool with annotations and no output schema, the description covers the input model, item limit, and return summary. It could say more about verdict semantics and whether one invalid item fails the entire batch, but the essential calling context is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The top-level `items` parameter lacks a schema description, but the description compensates by explaining that each item uses the same fields as validate_payout_beneficiary and that the array is capped at 100. The nested item fields are already well documented in the schema, so the description adds the missing batch-level meaning.

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 states a specific verb and resource: validating beneficiaries in a batch, with scope capped at 100. It distinguishes itself from the singular sibling by noting each item uses the same fields as validate_payout_beneficiary.

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?

It names concrete use cases such as payroll runs, supplier files, and marketplace withdrawals, which gives clear context for when to use batch validation. It does not explicitly say when to prefer the single-item sibling or what to do if more than 100 items must be validated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources