Skip to main content
Glama

data_schema

Idempotent

Validate file syntax and manage schema associations for JSON, YAML, and TOML files. Scan for schema directories and bind files to schema URLs or names.

Instructions

Unified schema operations tool.

Actions:

  • validate: Validate file syntax and optionally against schema

  • scan: Recursively search for schema directories

  • add_dir: Add custom schema directory

  • add_catalog: Add custom schema catalog

  • associate: Bind file to schema URL or name

  • disassociate: Remove file-to-schema association

  • list: Show current schema configuration

Examples:

  • action="validate", file_path="config.json"

  • action="associate", file_path=".gitlab-ci.yml", schema_name="gitlab-ci"

  • action="disassociate", file_path=".gitlab-ci.yml"

  • action="list"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNoCatalog URI (for add_catalog action)
nameNoCatalog name (for add_catalog action)
pathNoDirectory path (for add_dir action)
actionYesAction: validate, scan, add_dir, add_catalog, associate, disassociate, or list
file_pathNoPath to file (for validate/associate/disassociate actions)
max_depthNoMax search depth (for scan action)
schema_urlNoSchema URL (for associate action)
schema_nameNoSchema name from catalog (for associate action)
schema_pathNoPath to schema file (for validate action)
schema_pathsNoOptional per-document schema file paths for multi-document YAML (for validate action)
search_pathsNoPaths to scan (for scan action)
document_indexNoOptional YAML document index for validate action in multi-document files (0-based)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Annotations provide readOnlyHint=false, openWorldHint=true, idempotentHint=true, destructiveHint=false, which convey basic safety profile. The description adds the fact that the tool performs schema operations but does not elaborate on behavioral details such as side effects of adding directories/catalogs, error handling, or permissions. It complements but does not significantly extend beyond annotations.

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?

The description is well-structured with a concise summary, a bullet list of actions, and clear examples. Every sentence is informative and earns its place. The front-loaded format allows quick comprehension of the tool's purpose and capabilities.

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?

Given the tool's complexity (7 actions, 12 parameters) and the presence of an output schema, the description sufficiently covers each action's purpose and provides illustrative examples. It could be more complete by explaining when to use each action (e.g., prerequisites for add_dir vs. add_catalog) but is not missing critical information for typical usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema covers all 12 parameters with descriptions (100% coverage), so baseline is 3. The description adds value by providing concrete examples showing parameter combinations for specific actions (e.g., 'action="validate", file_path="config.json"'), which helps understand typical usage beyond the schema's individual parameter descriptions.

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?

The description clearly states it is a 'Unified schema operations tool' and enumerates all seven specific actions (validate, scan, add_dir, add_catalog, associate, disassociate, list). Each action has a brief purpose, and the examples solidify understanding. The tool is well differentiated from siblings, which cover constraints, data manipulation, and queries rather than schema operations.

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?

The description lists actions and provides examples, but does not explicitly state when to use this tool versus alternatives. Sibling tools are conceptually distinct (e.g., constraint_validate vs. schema validation), but the description offers no exclusions or context for choosing this tool. Usage is implied but not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bitflight-devops/mcp-json-yaml-toml'

If you have feedback or need assistance with the MCP directory API, please join our Discord server