Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Create a graph

create_graph

Builds a .lazy file from a spec (see get_guide) and checks it. When ok is true it returns a download link for the user (on a hosted server) or saves it as save_as (on a local server); include_file also returns the whole file. Otherwise it returns the errors to fix.

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": {
      "spec": "<spec>"
    },
    "name": "create_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
save_asNo
include_fileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only say it is a non-destructive write that is not idempotent; the description adds real behavior beyond that: on success it returns a download link (hosted) or writes save_as (local), on failure it returns errors, and include_file embeds the whole file. It doesn't state what happens to an existing file at save_as, which is the main remaining gap.

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?

Compact and front-loaded, with the primary action first and the success/failure branching after. The conditional clauses are dense but each one conveys distinct behavior rather than repeating the schema.

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?

There is no output schema and no annotation detail, yet the description explains both success paths and the error path, which is what an agent needs to interpret results. The only shortfall is that the spec object's shape is delegated entirely to get_guide without any hint of its contents.

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%, so the description must carry the load and largely does: spec is the required input (deferred to get_guide for structure), save_as is where the file lands on a local server, and include_file causes the full file to be returned. The nested spec object's keys are not described here, only pointed at indirectly.

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 and artifact: builds a .lazy file from a spec and validates it. An agent can tell this is a construction tool, but the description doesn't differentiate it from the validate_graph sibling even though it mentions checking the result.

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?

It routes the agent to get_guide for the spec format and explains the server-dependent outcomes, which is useful context. However, it never says when to use this instead of validate_graph or graph_to_spec, so the choice among siblings is left to inference.

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