Skip to main content
Glama
Sign In

BUMIT

by ai.bumit
OverviewDiscussionsAdmin

Get Swiss company profile

get_company_profile
Read-onlyIdempotent

Retrieve the canonical Swiss commercial-register (Zefix) profile for one company by UID: legal name, legal form, register status, seat, canton, registered address, purpose and official register links, with provenance, attribution and a freshness envelope (evidence age, freshness threshold, stale flag and source state). The UID is normalized and its check digit validated before any source request. FOUND means a register record was retrieved, not that the business passed verification. For sanctions, FINMA and full verification outcomes, use verify_business.

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

Input Schema

NameRequiredDescriptionDefault
uidYesSwiss UID (e.g. CHE-116.281.549). Formatting is normalized; the mod-11 check digit is validated before any source request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, but the description adds genuine behavior: UID normalization and mod-11 check-digit validation happen before any source request (fail-fast), and the response carries provenance, attribution and a freshness envelope (evidence age, threshold, stale flag, source state). It also pre-empts a likely misread by stating FOUND means a record was retrieved, not that the business passed verification.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Front-loaded with the core action and return contents, then the semantics caveat, then the alternative. Dense but every clause carries information; the single enumeration sentence is long but readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 compensates by listing the returned fields and the freshness/provenance envelope, plus the FOUND semantics and the sibling alternative. Nothing an agent needs in order to call this correctly or interpret the result is missing.

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% and the schema itself already documents UID normalization and mod-11 validation, so the description mostly restates that. It adds only the sequencing detail ('before any source request'), which is a marginal contribution over the structured field.

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 and resource ('Retrieve the canonical Swiss commercial-register (Zefix) profile for one company by UID') and enumerates the returned fields, so the agent knows exactly what this call yields. It is clearly distinguishable from verify_business, which is named as the tool for verification outcomes.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'For sanctions, FINMA and full verification outcomes, use verify_business.' It also sets the boundary that this is retrieval only, so the agent knows not to expect a verification verdict here.

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

All BUMIT toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources