Skip to main content
Glama
Sign In

MentionAgent

by ai.mentionagent
OverviewDiscussionsAdmin

Hand the request to the person they named

redirect_thread
Destructive

Sends nothing. For when somebody replies 'I am not the right person, talk to X'. Opens a NEW thread to that address, carrying the referral, and closes the original as redirected. It does not change where replies on the old thread go: send_reply still answers the person who referred you. Refuses a loop, a repeat, an opted-out or bounced address, and a referral chain more than three deep.

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": {
      "conversationId": "<conversationId>",
      "email": "<email>"
    },
    "name": "redirect_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTheir name, if the reply gave one.
emailYesThe address they named.
conversationIdYesThe thread that named somebody else. From list_inbox or get_thread.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: "Sends nothing", opens a new thread, closes the original, and enumerates refusal cases (loop, repeat, opted-out, bounced, chain deeper than three). This confirms and elaborates the destructiveHint=true / non-idempotent profile rather than contradicting it.

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

Conciseness4/5

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

Front-loads the counterintuitive fact ("Sends nothing") before the mechanics, and each sentence carries distinct information. Slightly dense and could be split, but there is no 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?

For a non-idempotent mutating tool with full schema coverage and no output schema, the description covers side effects, refusal conditions, and the reply-routing caveat. What happens on a refused redirect (error surface) is the only notable omission.

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% with self-documenting field descriptions (name, email, conversationId with provenance from list_inbox/get_thread). The description refers to "that address" and the referral context but adds no syntax or format 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?

Specific verb (redirect/hand off) plus resource (thread), with a concrete mechanism: opens a NEW thread to the named address, carries the referral, closes the original as redirected. An agent can distinguish this from send_reply and archive_thread purely from the description.

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

Usage Guidelines5/5

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

States the triggering condition explicitly ("somebody replies 'I am not the right person, talk to X'") and pre-empts the obvious confusion by noting send_reply still answers the original referrer. When-to-use and the relevant alternative are both named.

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

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