Skip to main content
Glama

create_cluster_report

Generates a two-phase Map-Reduce synthesis report from a frozen cluster snapshot and a physics investigation prompt.

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 physical investigation prompt (e.g. 'Analyze electroweak symmetry breaking, gauge representations, and mass hierarchy across discovered particle clusters.')
cluster_snapshot_idYesCluster Snapshot ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add useful context beyond the schema: a two-phase map-reduce synthesis implying a long-running compute job, and a 'frozen cluster snapshot' prerequisite. However, it never says the call is asynchronous, what handle is returned (report ID vs job ID), or whether the report must later be polled via get_job_status.

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; the action and the object of that action come first. The '2-Phase Map-Reduce' phrasing is jargon but still informative rather than decorative.

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/initiation tool with zero annotations and no output schema, the description leaves the most consequential facts unstated: whether the call blocks or returns immediately, what identifier comes back, and how to retrieve the finished report. 'Frozen snapshot' hints at a state prerequisite but does not confirm it.

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%, and the schema already gives a detailed example for 'prompt' and a bounded integer definition for 'cluster_snapshot_id'. The description adds no meaning about parameter format or constraints, so the baseline 3 applies.

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 clearly distinguishes it from get_cluster_report, list_cluster_reports, and delete_cluster_report. The '2-Phase Map-Reduce' qualifier adds flavor but does not obscure the core action.

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 explicit when-to-use guidance, no statement of prerequisites (e.g. that the snapshot must already be frozen), and no routing to alternatives such as generate_deep_synthesis or the get/list report tools. The agent must infer from the name that this starts work rather than reading a completed report.

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