Skip to main content
Glama
Sign In
Qiniso

Qiniso

Official
by qinisolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

validate_cz_rc

Verify a Czech or Slovak rodné číslo (birth number) by checking its 10-digit mod-11 rule and pre-1954 format. Ensures structural validity before reliance.

Instructions

USE THIS to verify a Czech or Slovak rodné číslo (birth number) before relying on it. Checks the modern 10-digit form's mod-11 rule (9-digit pre-1954 numbers have no 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": {
      "rc": "<rc>"
    },
    "name": "validate_cz_rc"
  }
}

Input Schema

NameRequiredDescriptionDefault
rcYesThe 10-digit rodné číslo (slash/spaces ignored).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.0

TDQS

A4/5.0
Behavior3/5

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

Describes what it checks (modern 10-digit mod-11, pre-1954 no check digit) and explicitly states 'validates structure only.' No annotations, so description carries burden; missing info on return format or error handling.

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, front-loaded with purpose, no redundant words. Every sentence adds essential information.

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 validation tool with no output schema, the description covers key behavioral aspects. Could mention return type but not necessary given tool simplicity.

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 already explains parameter format (10-digit, slash/spaces ignored). Description adds value by explaining the validation algorithm and historical distinction, going beyond the 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?

Clearly identifies the tool as validating Czech or Slovak rodné číslo (birth number). Specifies the algorithm (mod-11 for modern 10-digit) and distinguishes from many sibling validation tools for other identifiers.

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?

States to use it before relying on a rodné číslo, but does not explicitly mention when not to use it or suggest alternatives. Usage is implied but lacks exclusion criteria.

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