Skip to main content
Glama

ch_uid_batch

Validates up to 25 Swiss UID/VAT numbers in one call against the official Swiss UID register, returning per-record results for batch compliance checks.

Instructions

Batch Swiss UID / VAT number validation (up to 25 numbers per call) against the official Swiss UID register. Same per-record output as /api/ch-uid. The register allows ~20 lookups/min, so a full batch can take up to ~80 s. Sole-proprietor names are masked. Costs 0.05 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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": {
      "uids": "<uids>"
    },
    "name": "ch_uid_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
uidsYesUp to 25 Swiss UIDs, comma/space/newline separated (POST may also send a JSON array)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full load and does so unusually well: it discloses the rate limit (~20 lookups/min), worst-case latency (~80 s for a full batch), the sole-proprietor name-masking behavior, the 0.05 USDC x402 cost per successful call, and the exact failure mode (402 challenge returned without a payment key). That covers latency, cost, redaction, and auth in five sentences.

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?

Five short sentences, each carrying a distinct operational fact (scope, output parity, rate limit/latency, masking, payment). The most decision-relevant constraints come early and nothing is repeated from the schema verbatim beyond the 25-item cap.

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 single-parameter, no-output-schema tool the operational picture is essentially complete: cost, timeout budget, redaction, and auth failure mode are all present. The only soft spot is 'same per-record output as /api/ch-uid', which points at another endpoint rather than describing the returned fields — an agent must already know that shape.

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?

Schema coverage is 100% and the single uid parameter is fully documented in the schema, including accepted separators and the JSON-array variant. The description reinforces the 25-item cap, which matters for shaping input, though it adds little that the schema does not already state — slightly above the baseline 3 for a one-parameter tool.

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?

States a specific verb (batch validation), the resource (Swiss UID / VAT numbers) against the official Swiss UID register, and the batch ceiling of 25 per call. It also identifies itself relative to the ch_uid sibling by noting identical per-record output, so an agent can place it in the family without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the word 'Batch' and the 'same per-record output as /api/ch-uid' note, which suggests the single-record sibling is the alternative for non-batch cases. However, it never explicitly says when to prefer ch_uid over this tool, nor when not to batch — the routing decision is left to inference.

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