Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Check a graph file

validate_graph
Read-onlyIdempotent

Checks a .lazy file (its JSON text, or a download link from create_graph) the way LazyAnalysis reads it.

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": {
      "graph_file": "<graph_file>"
    },
    "name": "validate_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
graph_fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint false, non-open-world), so the bar is lower. The description adds a meaningful behavioral nuance by framing validation as 'the way LazyAnalysis reads it', which implies the runtime reader's semantics rather than a generic schema check. However, with no output schema it never says what a failed check returns (error list, boolean, exception), which is the key behavioral unknown for a validator.

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?

One front-loaded sentence with no waste; the parenthetical clarifies the accepted formats. Slightly dense but appropriate in length for the tool's simplicity.

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

Completeness5/5

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

For a one-parameter, read-only validation tool with full annotation coverage, the description supplies the accepted input forms and the validation semantics. The only remaining gap is result format, which is a minor omission rather than something that would cause a mis-call.

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?

Schema coverage is 0% and the schema only says 'Graph File', but the description explains that this string may be either the raw JSON text of the file or a download link produced by create_graph. That resolves the main ambiguity in a single opaque parameter and materially exceeds the schema.

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?

States a specific verb (checks) and resource (a .lazy file) and ties it to the create_graph output, which distinguishes it from conversion siblings like graph_to_spec. It stops short of saying what 'checks' means concretely (syntax vs. semantic validation) or what a failure looks like, so it is clear but not airtight.

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?

Mentioning that the input comes from create_graph implies the typical workflow (validate a graph you just built), but there is no explicit when-to-use/when-not guidance and no named alternative for related needs. Usage is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources