Skip to main content
Glama
MCP Agent Operations

MCP Agent Operations

verify_yaml

Validate YAML files for duplicate keys and return structured diagnostics, helping catch configuration errors before agent operations run.

Instructions

Validate exact YAML files, including duplicate keys, with structured diagnostics.

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": {
      "repository_root": "<repository_root>",
      "paths": "<paths>"
    },
    "name": "verify_yaml"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
repository_rootYes

Output Schema

NameRequiredDescriptionDefault
okYes
scopeNopatterns
findingsNo
added_filesNo
checked_filesNo
checkpoint_idNo
deleted_filesNo
renamed_filesNo
modified_filesNo
selected_filesNo
unmatched_patternsNo
affected_inbound_filesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.15.1
    • addedOutput schema / properties / added_files
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / affected_inbound_files
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / checkpoint_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null
      +}
    • addedOutput schema / properties / deleted_files
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / modified_files
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / renamed_files
      Added value: +{
      +  "items": {
      +    "additionalProperties": {
      +      "type": "string"
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / scope
      Added value: +{
      +  "default": "patterns",
      +  "type": "string"
      +}
    • addedOutput schema / properties / selected_files
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / unmatched_patterns
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  2. First observedv0.5.1

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only says the tool validates and returns structured diagnostics. It does not state that the operation is read-only/non-mutating, whether it recurses into directories, how it handles non-existent paths, or whether validation stops at the first error; the note about duplicate keys is the only real behavioral detail.

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?

A single front-loaded sentence with no filler. The only cost is the unexplained word "exact", which adds ambiguity rather than information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but two required parameters at 0% schema coverage plus no annotations mean the definition should do much more than one sentence. An agent still lacks the information needed to construct a correct call with confidence.

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

Parameters2/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 compensate, and it only partially does: "exact YAML files" hints that `paths` are exact file paths rather than globs, but `repository_root` is never mentioned and path-relativity or format expectations are left to inference.

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?

"Validate exact YAML files" gives a specific verb (validate) and a specific resource (YAML files), and the phrase "including duplicate keys" narrows the scope of the check. It does not name or differentiate itself from any sibling, and the qualifier "exact" is never explained, so an agent must guess whether it means exact file paths versus globs.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no prerequisites, and no statement of what happens when a path is missing or not YAML. The only implied usage is 'you have YAML files to check', which is thin for a tool with a sibling set that includes other verification tools.

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