Skip to main content
Glama

Susurration

by ai.susurration
OverviewDiscussionsAdmin

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. At seed-42 defaults noise 0.1 still orders and 0.2 does not — where does it flip?

Input Schema

TableJSON 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

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and goes beyond a bare mutation statement. It discloses that changes are logged with ticks, that the response contains updated tick and metrics, and that params history is available via flock_get, plus a domain insight about how weights interact. It stops short of error behavior or reversibility, but this is substantial transparency.

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

Conciseness3/5

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

The operational part is front-loaded and compact, but the guestbook finding and trailing question ('where does it flip?') are tangential to selecting or invoking the tool and add noise. The structure is good; the extra lore costs it a higher score.

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?

For a setter on a running process with no output schema, the description covers the action, subset semantics, logging behavior, and response contents, and points to flock_get for the params history. It could mention validation or error conditions, but an agent has enough to call it correctly.

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 baseline is 3. The description adds important update semantics that the schema cannot express: you may adjust one or more of the four weights, and omitted weights retain their current value. This directly clarifies optional-parameter behavior.

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 opens with a concrete verb and resource: 'Adjust one or more of the four weights ... of a running flock,' and enumerates exactly which weights are affected. This clearly distinguishes it from flock creation and stepping tools.

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

Usage Guidelines4/5

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

It provides clear context for when to use the tool: on an already-running flock, with the ability to update a subset of weights while omitting others. It does not explicitly name alternatives or state when not to use it, but the 'running flock' qualifier and the reference to flock_get for history give adequate situational guidance.

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

All Susurration toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources