Skip to main content
Glama
Sign In
Qiniso

Qiniso

Official
by qinisolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

validate_ch_ahv

Verify a Swiss social-insurance number (AHV/AVS) by validating its 13-digit format, 756 prefix, and EAN-13 check digit.

Instructions

USE THIS to verify a Swiss social-insurance number (AHV/AVS, 756.…) before relying on it. Checks the 13-digit form starting 756 and the EAN-13 check digit. Validates structure only.

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

Input Schema

NameRequiredDescriptionDefault
ahvYesThe 13-digit Swiss AHV/AVS number (dots ignored).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations provided, but description discloses that the tool only performs structural validation (no real-world verification). Mentions checks on format and check digit, setting clear expectations.

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 sentences, no filler, front-loaded with purpose. Efficient and clear.

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?

Tool is simple with one required parameter and no output schema. Description covers what the tool does, its limitations, and how the input is processed, making it complete for an agent to decide invocation.

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 description coverage is 100% with parameter details. Description adds that the number starts with 756 and uses EAN-13 check digit, and notes dots are ignored, providing extra value beyond schema.

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?

Description clearly states the tool validates Swiss AHV/AVS numbers, specifying the format (13-digit starting 756) and EAN-13 check digit. Distinct from many sibling validate_* tools by targeting a specific country and number type.

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?

Explicitly says 'USE THIS to verify a Swiss social-insurance number... before relying on it', indicating when to use. Notes it only validates structure, implying it does not check existence. No explicit when-not-to-use, but context with siblings makes it clear.

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

Deploy Server

Other Tools