Skip to main content
Glama

Susurration

experiment_run

Run one bounded, reproducible experiment in a single call instead of many step calls: set the four weights, ticks, a sample_every interval, optional interventions (weights that change at given ticks) and optional windows (tick ranges to summarise). The synchronous 10s budget bounds the work by ticks × n² (the neighbour search is O(n²)); larger runs are rejected with a clear message and belong on the asynchronous path once enabled. Returns a compact summary plus an experiment_id; fetch the full measured series with experiment_get. The recipe is stored replay-verifiably, so a trace can cite the experiment_id and the server re-runs the whole recipe to verify it. A natural first use, from trace OwhI_pMmilbWzhiXRLHNp: Within noise 0.084-0.090, how much of the swing is window placement: with 5000 ticks and a 3000-5000 window, do the means become monotone in noise for seeds 42, 7 and 2026? At n 120 the synchronous budget allows at most 4166 ticks, so a 3000-4000 window fits now; 5000 ticks belongs on the asynchronous path.

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": {
      "ticks": "<ticks>"
    },
    "name": "experiment_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNonumber of birds (10 to 400, default 120)
seedNouint32 PRNG seed; omit for a random one. Same seed and recipe replay byte-identically
noiseNonoise weight (0 to 1): random heading jitter per tick; 0 is fully deterministic (spec v1 behaviour)
ticksYestotal ticks to simulate (1 to 5000)
windowsNotick ranges [start, end] to summarise separately (max 20)
cohesionNocohesion weight (0 to 1): pull toward the centre of nearby birds
alignmentNoalignment weight (0 to 1): steer toward the average heading of nearby birds
separationNoseparation weight (0 to 1): steer away from birds that come too close
sample_everyNomeasure metrics every N ticks (default 10)
interventionsNoweight changes applied mid-run (max 20 entries)
time_to_polarizationNopolarization threshold (0 to 1); the summary reports the first sampled tick at or above it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/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 critical behavior: a synchronous 10s budget, computational complexity (ticks × n²), rejection of larger runs, return format (compact summary plus experiment_id), and replay-verifiability. It also explains how to retrieve the full series. This is comprehensive transparency.

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?

The description is well-structured and front-loads the core purpose and constraints. However, the lengthy concrete example (several sentences) adds substantial length and could be trimmed for conciseness, though it does illustrate a real use case.

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

Completeness5/5

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

Given the tool's complexity (11 parameters, no output schema, no annotations), the description covers everything an agent needs: purpose, usage alternatives, behavioral limits, return values, reproducibility, and a sample use case. No critical gaps remain.

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 the baseline is 3. The description summarizes the parameters ('set the four weights, ticks, a sample_every interval, optional interventions... and optional windows...') but does not add meaning beyond what the schema already provides—no extra syntax, format details, or edge cases are introduced.

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

Purpose5/5

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

The description states a specific verb+resource ('Run one bounded, reproducible experiment in a single call') and distinguishes it from sibling tools by naming the alternative approach ('instead of many step calls') and the retrieval sibling ('experiment_get'). An agent can immediately tell what this tool does and how it differs from step-based tools.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool (bounded single call), when not to use it (larger runs are rejected and belong on the asynchronous path), and which alternative to use for fetching results (experiment_get). The guidance is clear and actionable.

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