Skip to main content
Glama

generate_deep_synthesis

Generate or upgrade a 3-phase hierarchical synthesis report over a cluster snapshot, with intermediate batch aggregation of archetype clusters.

Instructions

Upgrade or run a 3-Phase Hierarchical Deep Synthesis report over a cluster snapshot with intermediate batch aggregation.

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": {
      "report_id": "<report_id>"
    },
    "name": "generate_deep_synthesis"
  }
}

Input Schema

NameRequiredDescriptionDefault
report_idYesParent Cluster Report ID
batch_sizeNoBatch size of archetype clusters to synthesize in Phase 2 (default: 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and it discloses very little. It does not say whether this is a long-running/async job (a get_job_status sibling exists), whether it mutates or overwrites an existing report, what the cost of 'deep synthesis' is, or what permissions are needed.

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 dense sentence with the action front-loaded and no filler. It is efficient, though the internal jargon ('3-Phase Hierarchical Deep Synthesis') is unexplained, which costs a bit of clarity.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and an apparently heavy multi-phase operation, the one-line description is not enough. An agent cannot tell whether the call blocks, returns a job handle, or how failure/partial completion is reported.

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 description coverage is 100%, so both report_id and batch_size are already documented in the schema. The description's mention of 'intermediate batch aggregation' loosely corroborates what batch_size means, but adds no syntax, constraints, or effects beyond the 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 description names a specific action pair ('Upgrade or run') and a specific artifact ('3-Phase Hierarchical Deep Synthesis report over a cluster snapshot'), so the general purpose is inferable. However, it never distinguishes this from adjacent siblings such as create_cluster_report or compute_clusters, and the distinction between the 'upgrade' and 'run' modes is left undefined.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this instead of create_cluster_report, compute_clusters, or the embedding generators. Prerequisites are also absent: nothing says whether a report or snapshot must already exist, or what conditions trigger the 'upgrade' path versus a fresh run.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.