Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Discover server capabilities

get_capabilities
Read-onlyIdempotent

Start here for LazyAnalysis reactive graphs, dashboard authoring and publishing, themes, nested supernodes, and the actions this MCP server supports.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile of this zero-param read is fully covered. The description adds a hint that it is an entry point, but says nothing about what is returned, how large the payload is, or whether the content is static; against a lowered annotation-backed bar this is adequate but thin.

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?

It is a single front-loaded sentence with the critical 'Start here' instruction first and no redundant wording. Slightly awkward phrasing in 'the actions this MCP server supports' costs it a point but nothing is wasteful.

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

Completeness3/5

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

For a simple zero-param read tool with full annotation coverage, the description covers the entry-point role and enumerates topic areas. With no output schema present, though, it never describes the shape or granularity of the returned capability data, leaving the agent to discover that on first 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?

The tool takes zero parameters and schema coverage is 100%, so there is no parameter semantics to add; baseline 4 applies. Nothing in the description contradicts or muddies the empty input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence 'Start here for LazyAnalysis reactive graphs, dashboard authoring and publishing, themes, nested supernodes, and the actions this MCP server supports' is a topic/content listing rather than a clear verb+resource statement of what the tool returns. It hints at a capability manifest, but the agent must infer that from 'the actions this MCP server supports' and cannot tell how this differs from siblings like read_help or get_geospatial_capabilities.

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?

'Start here' is explicit sequencing guidance telling the agent to call this before authoring graphs or dashboards, which is genuinely useful. However, it offers no exclusions or alternatives (e.g., when to use get_guide, read_help, or get_geospatial_capabilities instead), so the routing guidance is incomplete.

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