Skip to main content
Glama

create_cluster_report

Generate a two-phase Map-Reduce synthesis report from a frozen cluster snapshot and scholarly biological prompt, turning clustered ecological or taxonomic data into structured findings.

Instructions

Initiate a 2-Phase Map-Reduce synthesis report on a frozen cluster snapshot.

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": {
      "cluster_snapshot_id": "<cluster_snapshot_id>",
      "prompt": "<prompt>"
    },
    "name": "create_cluster_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
promptYesScholarly biological inquiry prompt (e.g. 'Investigate convergent trophic strategies, morphological thermoregulation adaptations, and sensory specializations across arctic tundra and hot desert clusters.')
cluster_snapshot_idYesCluster Snapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden and discloses almost nothing: it does not say whether the call is asynchronous, whether it returns a report ID or a job ID (get_job_status exists as a sibling), how long a two-phase map-reduce takes, or what resources it consumes. 'Initiate' hints at a long-running kickoff, but that is inference rather than disclosure.

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 front-loaded sentence with no filler or repetition. It is arguably too terse for the operation's complexity, but nothing in it is wasted.

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 creation tool with no annotations and no output schema, the definition leaves out the essentials: what the caller gets back, whether it must poll a job, and any cost or duration expectations. The absence of an output schema means the description should have explained the return contract and does not.

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 parameters are already documented, including an example prompt. The description only reinforces that cluster_snapshot_id refers to a frozen snapshot; it adds no format, constraint, or semantic detail beyond the schema.

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 ('Initiate') and resource ('synthesis report') scoped to 'a frozen cluster snapshot', which is enough to separate it from get_cluster_report, list_cluster_reports and delete_cluster_report. The '2-Phase Map-Reduce' framing adds flavor but not a crisper definition of what is produced.

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?

No guidance on when to use this versus generate_deep_synthesis or the read-only report tools, and no stated prerequisites such as the snapshot having to exist and be complete. The agent must infer that 'frozen' means an already-created snapshot from the parameter name alone.

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