Skip to main content
Glama
Sign In
mcp-el-salvador-dte

mcp-el-salvador-dte

by Gerar12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Validate Salvadoran DUI

validate_dui

Validate a Salvadoran DUI by verifying its format and modulo-10 check digit. Returns validity status and reason if invalid.

Instructions

Validate a Salvadoran DUI (Documento Único de Identidad). Checks the format (8 digits, hyphen, 1 check digit — e.g. 01234567-8) and the official modulo-10 check digit. Returns { valid, reason? }.

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

Input Schema

NameRequiredDescriptionDefault
duiYesDUI to validate, e.g. "01234567-8".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Describes the validation checks (format and modulo-10 check digit) and the return object structure {valid, reason?}. No annotations provided, but description covers key behaviors.

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 concise sentences with all essential information. No extraneous text.

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?

Complete for a single-parameter validation tool. Explains input format, validation logic, and output structure. No output schema exists, but return type is specified.

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?

Adds format details and example (e.g. 01234567-8) beyond the schema's simple parameter description. Schema coverage is 100%, but description enhances understanding.

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?

The tool explicitly states it validates a Salvadoran DUI, a specific document type. It distinguishes from siblings like validate_nit by naming the document.

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?

The purpose is clear but no explicit guidance on when to use this vs alternatives like validate_nit. Usage is implied by the document type.

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