Skip to main content
Glama

TraceVero

Check a sanitized configuration

validate_config
Read-onlyIdempotent

Check JSON structure and Docker environment forwarding for a client. Submit a locally sanitized configuration, never live tokens. Returns redacted repairs; no installation or execution.

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": {
      "config": "<config>",
      "client": "<client>"
    },
    "name": "validate_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes
configYes

Output Schema

NameRequiredDescriptionDefault
issuesYes
statusYes
rule_versionYes
catalog_versionYes
dataset_versionYes
corrected_configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description adds value beyond them: it discloses that responses contain 'redacted repairs' and reiterates 'no installation or execution'. The 'never live tokens' warning adds a security constraint that structured fields do not convey.

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?

Three short sentences, each force-loaded with a distinct fact (checks, input hygiene, output behavior) with no filler. The opening sentence is slightly dense but front-loads the core purpose correctly.

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?

An output schema exists, so the description need not enumerate return fields, and it correctly points out that repairs come back redacted. The main gap is the fully undocumented parameter schema, particularly the anyOf string-or-object config form, which the description does not address.

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 0%, so the description must carry the load. It does clarify intent for both parameters ('for a client' and 'a locally sanitized configuration'), and the sanitization requirement is meaningful semantics. It still omits the config's string-vs-object duality, size limits, and what a valid client identifier looks like.

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 names a specific verb ('Check') and two concrete resources ('JSON structure' and 'Docker environment forwarding for a client'), which is far more than the tautological title 'Check a sanitized configuration'. It implicitly separates itself from mutating siblings like 'configure' by stating 'no installation or execution', though no sibling is named directly.

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?

There is a clear precondition ('Submit a locally sanitized configuration, never live tokens') that tells the agent how to prepare input, which is real guidance. However, it never states when to reach for this tool versus 'configure', 'compare', or 'plan_workflow', so selection against alternatives is left to inference.

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