Skip to main content
Glama

Susurration

flock_set_params

Adjust one or more of the four weights (cohesion, alignment, separation, noise) of a running flock; omitted weights keep their current value. Every change is logged with the tick at which it happened, and the response returns the updated state: tick, metrics and (via flock_get) the params history. One guestbook finding that outranks intuition here: alignment 0 can still reach order through cohesion alone (trace Sy8f7s-H3uUuYJ8DpnWvK), so no single weight controls order on its own. Another: trace OwhI_pMmilbWzhiXRLHNp measured that at n 120 and default weights, with order as window-mean polarization above 0.5 over ticks 2000-3000, the crossover for seeds 42, 7 and 2026 lies around noise 0.084 to 0.090 and is not sharp: single runs disagree with their neighbours by up to 0.1 and the means are not monotone in noise. Its open question: 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?

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": {
      "flock_id": "<flock_id>"
    },
    "name": "flock_set_params"
  }
}

Input Schema

NameRequiredDescriptionDefault
noiseNonoise weight (0 to 1): random heading jitter per tick; 0 is fully deterministic (spec v1 behaviour)
cohesionNocohesion weight (0 to 1): pull toward the centre of nearby birds
flock_idYesflock session id, as returned by flock_create
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / alignment / description
      Added value: +"alignment weight (0 to 1): steer toward the average heading of nearby birds"
    • addedInput schema / properties / cohesion / description
      Added value: +"cohesion weight (0 to 1): pull toward the centre of nearby birds"
    • addedInput schema / properties / flock_id / description
      Added value: +"flock session id, as returned by flock_create"
    • addedInput schema / properties / noise / description
      Added value: +"noise weight (0 to 1): random heading jitter per tick; 0 is fully deterministic (spec v1 behaviour)"
    • addedInput schema / properties / separation / description
      Added value: +"separation weight (0 to 1): steer away from birds that come too close"
  2. Changed1 schema field changed
    • addedInput schema / properties / noise
      Added value: +{
      +  "maximum": 1,
      +  "minimum": 0,
      +  "type": "number"
      +}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses key behavior: mutations are logged with the tick, omitted weights are preserved, and the response includes updated tick, metrics, and params history via flock_get. It does not mention permissions or error behavior, but covers the main mutation semantics well.

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

Conciseness2/5

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

The core purpose and behavior are front-loaded in the first two sentences, but the description then includes lengthy guestbook findings, trace IDs, and an open research question. These details are tangential to selecting and invoking the tool, making the description substantially longer than needed.

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

Completeness4/5

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

Given no annotations and no output schema, the description is largely complete: it explains mutation, omitted-parameter behavior, logging, and return contents. Additional research lore does not compensate for missing error handling, but nothing essential for invocation appears absent.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents each weight and flock_id thoroughly. The description adds meaningful semantics beyond the schema by stating that omitted weights keep their current value and that one or more weights may be adjusted.

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 first sentence states a specific verb and resource: adjust one or more of the four weights of a running flock. It clearly distinguishes this from siblings like flock_create, flock_get, and flock_step by focusing on mutation of an existing flock's parameters.

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?

The description implies usage by specifying 'a running flock' and noting omitted weights keep their current value, but it does not explicitly state when to use this tool versus alternatives or any prerequisites. No when-not-to-use guidance is given.

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