Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Read the LazyAnalysis help

read_help
Read-onlyIdempotent

The help of LazyAnalysis (what people see with F1): what the platform is for and how it works, the node editor, dashboards and how cards react to the graph, supernodes and their parameters, Theme Studio, the Python node, sharing, AI assistants and the example graphs. Without a page: the list of pages. With a page id (e.g. "how_it_works", "dashboards"): that page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that by defining the two response modes — a page index when no id is supplied, the page body when an id is supplied — and by anchoring the content to 'what people see with F1'. It says nothing about behavior on an unknown page id.

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?

Front-loaded with the essential identity, then the topic list, then the two calling modes — a sound progression. The middle topic enumeration is long and could be trimmed, and the final two clauses are telegraphic fragments ('Without a page: ... With a page id: ...') rather than complete sentences, though they remain unambiguous.

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 single-optional-parameter read-only documentation tool with no output schema, the description supplies everything needed: what the resource is, the index-vs-page duality, and example ids. The safety and idempotency profile is already carried by annotations, so no further behavioral disclosure is required.

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 description coverage is 0%, so the description carries the full burden for the single 'page' parameter, and it does: empty/omitted means the index of pages, a value means that page, with two concrete example ids. It stops short of explaining where valid ids come from or what happens with an invalid id, but the discover-then-fetch pattern is conveyed.

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 gives a specific verb (read/list) and resource (the LazyAnalysis help pages, the F1 documentation) and even enumerates the topic areas covered, so an agent knows exactly what content lives behind it. It does not distinguish itself from siblings such as get_guide or get_capabilities, which leaves ambiguity about which documentation tool to call when several are available.

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?

Usage is only implied: the definition makes clear you can read a page list or a single page, so the calling pattern is inferable. It never states when to prefer this over the doc-oriented siblings (get_guide, get_capabilities, describe_node_type), and offers no exclusions or prerequisites.

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