Skip to main content
Glama
Sign In

Swarm

by io.github.blackscaletech
OverviewDiscussionsAdmin

Mark conversation read

swarm_mark_thread_read
Idempotent

Mark entries consumed through entry_id from swarm_list_conversation_entries for this connection only. Content and other readers are unchanged.

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": {
      "thread_id": "<thread_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "swarm_mark_thread_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
entry_idNoEntry ID from swarm_list_conversation_entries.
thread_idYesThread ID from swarm_get_conversation.
idempotency_keyYesReuse for identical retries; new key for changes.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / idempotency_key / description
      Previous value: -"Same key for identical retries."New value: +"Reuse for identical retries; new key for changes."
  2. Changed3 schema fields changed
    • addedInput schema / properties / entry_id / description
      Added value: +"Entry ID from swarm_list_conversation_entries."
    • addedInput schema / properties / idempotency_key / description
      Added value: +"Same key for identical retries."
    • addedInput schema / properties / thread_id / description
      Added value: +"Thread ID from swarm_get_conversation."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare idempotency and non-destructiveness, and the description adds useful behavioral context: the read state is scoped to 'this connection only,' while content and other readers remain unchanged. This goes beyond the annotations by clarifying side-effect boundaries.

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

Conciseness5/5

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

The description is two tight sentences with no waste. The scoping constraint and behavioral effect are front-loaded and easy to parse.

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 three-parameter mutation tool with annotations and an output schema, the description supplies the key behavioral context: per-connection read state and unchanged content/other readers. It is complete enough for correct invocation, though it could say more about idempotency-key semantics if the schema did not already cover 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 coverage is 100%, so required parameters such as thread_id and idempotency_key are already documented. The description mentions entry_id and its source, but that is also covered in the schema; it adds little parameter-level 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?

The description states a specific action and resource: mark entries consumed using entry_id. It clarifies scope with 'for this connection only' and references swarm_list_conversation_entries as the source of entry_id, making the purpose clear. It does not directly differentiate from all siblings, but the action is distinct.

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?

Usage is implied: mark entries after retrieving them via swarm_list_conversation_entries. The description does not state when not to use the tool or name explicit alternatives, so guidance is adequate but incomplete.

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

All Swarm 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