Skip to main content
Glama

Find Swiss company in UID register

find_swiss_company
Read-onlyIdempotent

Searches the public Swiss UID register by company name (optionally with postal code or town) and returns up to 10 matches with UID, name, address and VAT registration status. Use it when the user knows a Swiss company's name but not its UID.

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

Input Schema

NameRequiredDescriptionDefault
nameYesCompany name or a distinctive part of it, at least 3 characters.
townNoOptional town.
postal_codeNoOptional Swiss postal code, 4 digits.
with_receiptNoOptional, default false. Set true only when the user asks for a signed receipt of this check for their files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / with_receipt
      Added value: +{
      +  "description": "Optional, default false. Set true only when the user asks for a signed receipt of this check for their files.",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety profile is covered. The description adds useful behavior beyond that: the lookup targets a public external register, returns at most 10 matches, and includes the specific fields returned. It omits what happens on zero matches or on ambiguous multi-hit results.

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?

Two tight sentences with no filler, and the core search behavior is front-loaded before the usage condition. Every clause carries information an agent needs.

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?

With no output schema, the description correctly compensates by enumerating returned fields and the 10-result cap. It is nearly complete for a read-only lookup, missing only edge-case behavior for no matches or how to narrow a query when the cap is reached.

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 description coverage is 100%, so every parameter (including the pattern-constrained postal_code and the conditional with_receipt) is already documented in the schema. The description restates the name/town/postal_code combination but adds no syntax, matching, or format detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ('Searches the public Swiss UID register by company name') plus the result shape (UID, name, address, VAT status, max 10). It does not name or differentiate against any sibling such as find_lei or check_vat_id, so an agent must infer the boundary itself.

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?

'Use it when the user knows a Swiss company's name but not its UID' gives a clear positive trigger and implicitly excludes the case where the UID is already known. No explicit when-not or named alternative is provided, so it stops short of full routing guidance.

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