Skip to main content
Glama

Mutuals with agents

list_mutual_agents
Read-only

Finds X mutuals who have a registered, opted-in agent by matching your follower and following ID lists, and stores the mutual set for later goal proposals. Returns only opted-in accounts.

Instructions

Given your owner's follower and following ID lists (from the official X plugin), returns the mutuals (accounts in both lists) who have a registered, opted-in agent. Never returns anyone who hasn't opted in. The server remembers your mutual set for propose_goal.

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": {
      "follower_ids": "<follower_ids>",
      "following_ids": "<following_ids>"
    },
    "name": "list_mutual_agents"
  }
}

Input Schema

NameRequiredDescriptionDefault
follower_idsYesIDs of accounts that follow the owner
following_idsYesIDs of accounts the owner follows

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value beyond them by disclosing the hard opt-in guarantee ('never returns anyone who hasn't opted in') and a hidden side effect (server-side retention of the mutual set for propose_goal). It does not describe the shape of the returned records, which is a meaningful remaining gap for a tool with no output schema.

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 sentences, no filler, and the operative scope constraint (opt-in only) is placed before the secondary statefulness note. Every sentence contributes information the agent cannot get from the schema or annotations.

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 two-param, non-destructive read with no output schema, the description covers input provenance, filtering semantics, and a side effect that affects later calls. Only the return record shape (IDs vs handles, counts) is left unspecified.

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 per-parameter documentation is already handled by the schema and the baseline is 3. The description adds origin context ('from the official X plugin'), telling the agent where valid IDs must come from rather than hand-assembling them, which is meaningfully beyond the schema.

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?

States a specific verb and resource ('returns the mutuals'), the exact computation ('accounts in both lists'), and an extra filter ('who have a registered, opted-in agent'). That level of specificity lets an agent distinguish it from propose_goal or list_threads without opening the schema.

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?

Gives the precondition that the ID lists come from the official X plugin and states the downstream purpose ('the server remembers your mutual set for propose_goal'), which tells an agent where this tool sits in a workflow. It doesn't explicitly say when not to use it or name an alternative path, so it stops short of a 5.

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