Skip to main content
Glama

Lexicon Garden

validate_lexicon

Validate a lexicon schema and optionally validate data against it. Use this to verify schema correctness and validate records, query params, or procedure inputs against their schemas.

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": {
      "schema": "<schema>"
    },
    "name": "validate_lexicon"
  }
}

Input Schema

NameRequiredDescriptionDefault
flagsNoOptional: Validation flags
inputNoOptional: Procedure input body to validate (for procedure schemas only)
paramsNoOptional: Query parameters to validate (for query or procedure schemas)
recordNoOptional: Record data to validate (for record schemas only)
schemaYesThe lexicon schema to validate (the full lexicon document as a JSON object)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that schema validation is the core operation and data validation is optional, but it does not describe failure behavior, whether external references are resolved by default, or whether the operation is strictly read-only.

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?

The description is two sentences and front-loads the primary operation. The second sentence adds useful specifics about validation targets, though it repeats the optional validation idea already stated in the first sentence.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with five parameters, nested objects, no annotations, and no output schema, the description covers the main purpose and input modes adequately. However, it leaves out behavioral details such as validation result format, error handling, and the role of validation flags, which are not supplied elsewhere.

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 description coverage is 100%, so the parameter descriptions already document schema, record, params, input, and flags. The description adds limited meaning by indicating that record, query parameter, and procedure input validation are optional data-validation modes, but it does not explain the flags or external-schema behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: validate a lexicon schema, with optional validation of data against it. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools such as check_compatibility.

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?

It states when to use the tool: to verify schema correctness and validate records, query params, or procedure inputs against their schemas. It gives clear usage context but does not name exclusions or alternative tools for overlapping validation/compatibility checks.

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