Skip to main content
Glama

validate_schema_data

Read-onlyIdempotent

Validates schema data against server-side JSON Schema rules without saving, enabling dry-run checks for canonical types, including trigger_config and csp_config.

Instructions

Dry-run: validate schema data without saving — same server-side JSON Schema validation as create_schema/update_schema. Supports all canonical types, including trigger_config and csp_config

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_type": "<schema_type>",
      "schema_data": "<schema_data>"
    },
    "name": "validate_schema_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
schema_dataYesSchema data to validate, using the same structure as create_schema
schema_typeYesCanonical schema type to validate. trigger_config and csp_config can be validated here but are created through create_trigger and create_csp.

Output Schema

NameRequiredDescriptionDefault
infosNo
validNo
errorsNo
warningsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.2.4
    • changedInput schema / properties / schema_data / description
      Previous value: -"Dados do schema a validar (mesma estrutura de create_schema)"New value: +"Schema data to validate, using the same structure as create_schema"
    • changedInput schema / properties / schema_type / description
      Previous value: -"Tipo do schema a validar (todos os tipos canônicos — trigger_config/csp_config são validados aqui mas criados via create_trigger/create_csp)"New value: +"Canonical schema type to validate. trigger_config and csp_config can be validated here but are created through create_trigger and create_csp."
  2. Changed1 schema field changedv2.2.3
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "anyOf": [
      +    {
      +      "required": [
      +        "valid",
      +        "errors"
      +      ]
      +    },
      +    {
      +      "properties": {
      +        "error": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "code": {
      +              "type": "string"
      +            },
      +            "message": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "code",
      +            "message"
      +          ],
      +          "type": "object"
      +        },
      +        "success": {
      +          "const": false
      +        }
      +      },
      +      "required": [
      +        "success",
      +        "error"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "properties": {
      +    "errors": {
      +      "type": "array"
      +    },
      +    "infos": {
      +      "type": "array"
      +    },
      +    "valid": {
      +      "type": "boolean"
      +    },
      +    "warnings": {
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changedv2.2.2
    • changedInput schema / properties / schema_type / enum
      Previous value: -[
      -  "persona_config",
      -  "api_config",
      -  "db_config",
      -  "workflow_config",
      -  "skill_config",
      -  "trigger_config",
      -  "mcp_tool_config",
      -  "mcp_resource_config",
      -  "csp_config"
      -]New value: +[
      +  "persona_config",
      +  "api_config",
      +  "workflow_config",
      +  "skill_config",
      +  "trigger_config",
      +  "mcp_tool_config",
      +  "mcp_resource_config",
      +  "csp_config"
      +]
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds real value by promising parity with server-side validation used at create/update time (so results predict actual writes) and by scoping which canonical types are accepted. It says nothing about failure modes or what a failed validation returns, leaving that to the output schema.

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 tight clauses, front-loaded with the dry-run qualifier that matters most for tool selection. Nothing is padded; every phrase either constrains behavior or routes the agent.

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?

With an output schema, rich annotations, and a fully documented two-parameter schema, the description supplies what is needed to call it correctly. It is only marginally short on distinguishing itself from other validate_* tools in the catalog.

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 schema already enumerates the eight canonical types and the create_trigger/create_csp caveat, so the description largely restates it. The 'supports all canonical types' phrasing adds only a mild reassurance beyond the enum, not new per-parameter meaning.

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 and resource ('validate schema data'), plus an explicit scope constraint ('dry-run... without saving') and a behavioral equivalence to `create_schema`/`update_schema`. An agent can immediately tell this is the non-persisting validation counterpart to the create/update pair.

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 dry-run framing plus the note that trigger_config/csp_config 'can be validated here but are created through create_trigger and create_csp' gives clear context for use. It does not, however, state any exclusion relative to the other validators in the catalog, so the when-not is only implicit.

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