Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Turn a graph into a spec

graph_to_spec
Read-onlyIdempotent

Turns a .lazy file (its JSON text, or a download link from create_graph) into a spec, to change it and build it again with create_graph.

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": "graph_to_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
graph_fileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by revealing the two accepted input forms and the intended downstream use (edit then rebuild), though it says nothing about the shape or size of the returned spec.

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 compact sentence with the action front-loaded and the input forms parenthesized rather than bloating the main clause. The line break is cosmetic and nothing is wasted, though the phrase 'into a spec, to change it' is slightly elliptical.

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?

For a one-parameter, read-only conversion tool with no output schema, this covers input format, purpose, and the follow-up call. The remaining gap is that 'spec' is never characterized, so an agent does not know whether it receives text, JSON, or a reference — a minor but real omission.

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 labels the field 'Graph File', so the description carries the burden. It does this well by specifying that the value is the .lazy file's JSON text or a download link from create_graph, which is exactly the disambiguation an agent needs for this single parameter.

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?

The description states a concrete verb and resource: converting a '.lazy' file into a 'spec'. It also names the counterpart tool (create_graph) that produces and consumes the file, so an agent can place it in the workflow. It stops short of saying what a 'spec' actually is, which keeps it from a 5.

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?

It gives a clear reason to use it: 'to change it and build it again with create_graph', which implicitly frames this as the edit-path tool versus create_graph's build path. There is no explicit 'when not to use' or mention of validate_graph as an alternative, so it is clear context rather than full routing guidance.

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