Skip to main content
Glama

LazyAnalysis — AI Solution Composer

Get a solution pattern

get_solution_pattern
Read-onlyIdempotent

Discover proven composition patterns. With pattern='nested_dashboard', return a complete spec showing a Graph supernode with its own dashboard, a Graph portal card on the parent dashboard, named input/output ports, and a parameter exposed through two graph levels. The native desktop application provides child-dashboard navigation and Back to parent/root controls in View mode. Customize after inspecting the current catalog, then create_graph.

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_solution_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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 is covered without description help. The description does add real behavioral context beyond that: the return value is a complete, customizable spec, and the pattern's runtime behavior (child-dashboard navigation and Back to parent/root controls in the desktop app) is disclosed. It stops short of saying what an empty or unrecognized pattern yields, which matters given the parameter defaults to an empty string.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose statement is correctly front-loaded in a short first sentence. The remaining text, however, is one long run-on spanning the spec contents, desktop UI navigation behavior, and the follow-up workflow, and the sentence about native desktop navigation controls is tangential to invoking the tool. Structure would improve by separating "what you get" from "what to do next."

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?

With a single optional parameter and no output schema, the description correctly takes on the job of describing the return value, and it does so for one pattern in detail. It is incomplete on two points an agent needs: the set of valid pattern values and the behavior when pattern is omitted or empty. For a lookup tool that is the main functional gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% — the parameter is documented only as a string titled "Pattern" with an empty default — so the description must carry the burden. It partially does by supplying the concrete value 'nested_dashboard' and describing exactly what that value returns, which is meaningful beyond the schema. But it never enumerates other valid values or explains what the empty default does, so an agent cannot reliably pick a value.

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 opens with a specific verb and resource ("Discover proven composition patterns") and then concretely enumerates what one returned spec contains: a Graph supernode, portal card, named ports, and a parameter spanning two graph levels. It is clearly a spec-retrieval tool rather than a graph-mutating one, and it explicitly hands off to create_graph, which separates it from the other siblings. The only gap is that it never states that multiple patterns exist beyond the single named example.

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?

"Customize after inspecting the current catalog, then create_graph" gives an implied workflow (fetch pattern -> inspect catalog -> build), which is genuine sequencing guidance. However, it never says when to prefer this over get_guide or read_help, nor what to do if you already know the structure you want. Usage is implied 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