Skip to main content
Glama

validate_agent_schemas

Read-onlyIdempotent

Validate an agent's configured schemas and reports errors and warnings before publication, so configuration issues are caught early.

Instructions

Validate an agent's configured schemas and report errors and warnings before publication.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "validate_agent_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesUUID of the agent to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.2.4
    • changedInput schema / properties / agent_id / description
      Previous value: -"UUID do agente a validar"New value: +"UUID of the agent to validate"
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds useful context that it reports errors and warnings before publication, but with no output schema it does not describe the shape of those reports, whether validation blocks anything, or what permissions are needed.

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?

It is a single front-loaded sentence with no filler. The key action, object, outcome, and timing are all packed efficiently into one line.

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 simple one-parameter validation tool with annotations and no output schema, the description covers purpose, timing, and outcome adequately. It could be more complete by explaining what "configured schemas" encompasses or how errors and warnings are surfaced, but nothing critical is missing for basic invocation.

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% and the single agent_id parameter is fully documented in the schema. The description does not add any meaning beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific verb ("validate") and resource ("an agent's configured schemas") plus the outcome ("report errors and warnings"). It is clear, but it does not explicitly distinguish itself from sibling validators such as validate_schema_data or validate_process_definition.

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 gives a clear usage context: validate before publication. However, it does not name alternatives like validate_schema_data or say when not to use this tool, so the guidance is clear but not exhaustive.

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