Skip to main content
Glama
zihin-ai

Zihin MCP Server

by zihin-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

validate_schema_data

Read-onlyIdempotent

Validate schema data without saving it, using the same Ajv rules as schema creation or updates. Run before creating or updating schemas to catch errors, warnings, and info early.

Instructions

Valida schema_data sem salvar (dry-run) — MESMA validação Ajv do create_schema/update_schema. Use SEMPRE antes de criar/atualizar schemas para evitar tentativa e erro. O contrato formal de cada tipo está no resource zihin://schemas/{schema_type}. Retorna erros, warnings e infos de validação.

Input Schema

NameRequiredDescriptionDefault
schema_dataYesDados do schema a validar (mesma estrutura de create_schema)
schema_typeYesTipo do schema a validar (todos os tipos canônicos — trigger_config/csp_config são validados aqui mas criados via create_trigger/create_csp)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/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. The description adds real value beyond that by disclosing it runs the SAME Ajv validation as create/update without persisting, and that it returns errors, warnings and infos.

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?

Front-loaded with the core purpose and dry-run qualifier, then the usage rule and return contents. Dense but each sentence carries useful information with no filler.

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 no output schema, the description compensates by stating it returns erros/warnings/infos, and it links the external contract resource. Complete enough for correct invocation, though it doesn't describe the error payload structure.

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 both parameters are already fully documented in the schema, including the schema_type enum. The description adds no format or syntax detail beyond pointing to the contract resource, so the baseline 3 applies.

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 (validates) and resource (schema_data) and immediately clarifies the dry-run/no-save scope, which distinguishes it from the mutating create_schema/update_schema siblings it names.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs 'Use SEMPRE antes de criar/atualizar schemas' and names the create/update alternatives, giving a clear when-to-use rule. It also points to the zihin://schemas/{schema_type} resource for the formal contract.

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