Skip to main content
Glama
Sign In
ops-brain

ops-brain

by TheK3nsai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

list_replies_to_me

Read-onlyIdempotent

Find handoffs that reply to your sent handoffs by matching your agent name; optionally filter replies after a given ISO-8601 timestamp.

Instructions

List handoffs that reply to ones you sent. Returns handoffs whose in_reply_to references a handoff with your agent_name as from_agent. Optional ISO-8601 since filters by reply timestamp.

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": {
      "agent_name": "<agent_name>"
    },
    "name": "list_replies_to_me"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20, clamped to 1..=200)
sinceNoOptional ISO-8601 timestamp; only replies created after this time are returned.
agent_nameYesYour agent identifier (free-form slug). Returns handoffs whose `in_reply_to` references a handoff you originally sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds genuine value by exposing the underlying query semantics (the `in_reply_to` ↔ `from_agent` join) and the timestamp-based filtering behavior, though it says nothing about pagination or result ordering.

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?

Three tight sentences, front-loaded with the core purpose followed by precise semantics. Every sentence earns its place with no redundancy or filler.

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?

With no output schema, the description correctly explains what the tool returns (handoffs whose `in_reply_to` references one of yours). For a simple, read-only list tool this is nearly complete, though it omits default result count and ordering, which are relevant to the caller.

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 all three parameters are already documented in the schema, including `since` and `limit`. The description largely restates the `since` semantics rather than adding format or syntax detail beyond the schema, so the baseline of 3 applies.

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 (List) and resource (handoffs) with a precise scope: only replies to handoffs you sent. The second sentence defines the exact join condition (`in_reply_to` referencing a handoff with your `agent_name` as `from_agent`), which clearly distinguishes it from the sibling `list_handoffs`.

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 by the scoping (use when you want replies to your own handoffs), but the description never explicitly names alternatives like `list_handoffs` or `search_bus`, nor states when not to use it. A reader can infer the context but gets no routing guidance.

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

Deploy Server

Other Tools