Skip to main content
Glama

Search XML schemas

search_schemas
Read-onlyIdempotent

Search xmlvalid's catalog of official XML schemas (UBL, CII, Peppol, XRechnung, Factur-X, ISO 20022, HL7, sitemaps…) by name, namespace, root element or area. Returns each schema's slug to pass to validate_xml, its version and the business rules it checks. No sign-in or API key needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to look for, such as "peppol invoice", "xrechnung cii" or "pain.001". Leave out to list the first schemas.

Output Schema

NameRequiredDescriptionDefault
shownYesSchemas listed, at most 25; add words to narrow the search.
totalYesSchemas matching every word.
schemasYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "schemas": {
      +      "items": {
      +        "properties": {
      +          "area": {
      +            "type": "string"
      +          },
      +          "kind": {
      +            "description": "The schema language.",
      +            "enum": [
      +              "xsd",
      +              "dtd",
      +              "rng",
      +              "rnc"
      +            ],
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "namespace": {
      +            "description": "The target namespace; empty when it has none.",
      +            "type": "string"
      +          },
      +          "root": {
      +            "description": "The document element it expects.",
      +            "type": "string"
      +          },
      +          "rules": {
      +            "description": "The business rule sets checked after the schema, by name.",
      +            "items": {
      +              "type": "string"
      +            },
      +            "type": "array"
      +          },
      +          "schema": {
      +            "description": "The slug to pass to validate_xml as schema.",
      +            "type": "string"
      +          },
      +          "summary": {
      +            "type": "string"
      +          },
      +          "url": {
      +            "description": "The schema's page on xmlvalid.com.",
      +            "type": "string"
      +          },
      +          "version": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "schema",
      +          "name",
      +          "kind",
      +          "version",
      +          "namespace",
      +          "root",
      +          "area",
      +          "rules",
      +          "summary",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "shown": {
      +      "description": "Schemas listed, at most 25; add words to narrow the search.",
      +      "type": "integer"
      +    },
      +    "total": {
      +      "description": "Schemas matching every word.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "total",
      +    "shown",
      +    "schemas"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive traits, so the bar is lower. The description still adds real context beyond them: the return payload (slug, version, business rules checked) and the auth profile ('no sign-in or API key needed'). It omits result-count limits or pagination behavior.

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 the resource and facets, then the return/next-step and auth facts. No filler and no repetition of the title.

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?

An output schema exists, so return values need not be spelled out, and the description still names the key fields. For a zero-required-param lookup tool this is nearly complete; only behavior on large or empty result sets is unaddressed.

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 query parameter's own description already explains examples and the omit-to-list behavior. The description only adds the facet vocabulary (namespace, root element, area) that hints at what matching supports, so this is baseline rather than added value.

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 (Search) and resource (xmlvalid's catalog of official XML schemas), then enumerates concrete schema families and the four lookup facets (name, namespace, root element, area). An agent can distinguish this from validate_xml/explain_rule without opening the schema.

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?

The description signals the workflow explicitly: the returned slug is what you pass to validate_xml, which makes clear this is the discovery step before validation. It does not state any when-not-to-use condition or describe what to do if a search returns nothing, so it stops short of 5.

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