Skip to main content
Glama

RedReplier

by com.redreplier
OverviewDiscussionsAdmin

Update Mention Status

update_mention_status
Destructive

Set one mention's triage status. APPROVED marks it a real lead; REJECTED marks it noise and drops it from default list_mentions and count_mentions results (pass statuses to see it again); NEW returns it to the inbox. Fully reversible: any status can move to any other; reviewedAt is stamped when leaving NEW and cleared on NEW. Judge on the content and relevanceScore, calling explain_mention first when the score looks off; never approve a mention you have not read. mentionId comes from list_mentions. Returns the updated mention.

Input Schema

NameRequiredDescriptionDefault
statusYesNew status: APPROVED (real lead), REJECTED (noise, hidden from default lists), or NEW (back to inbox)
mentionIdYesMention ID (UUID)
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultNoThe updated mention with its new status and reviewedAt (null when NEW).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / status / description
      Previous value: -"New status: NEW, APPROVED, or REJECTED"New value: +"New status: APPROVED (real lead), REJECTED (noise, hidden from default lists), or NEW (back to inbox)"
    • changedOutput schema / properties / result / description
      Previous value: -"The mention with its updated status."New value: +"The updated mention with its new status and reviewedAt (null when NEW)."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: full reversibility between any statuses, the reviewedAt stamp/clear rule, the downstream effect on list_mentions/count_mentions, and mentionId provenance. Although destructiveHint=true, the description discloses the mutation is reversible and scoped, which meaningfully informs the agent.

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 core action, then layers status semantics, reversibility, and judgment guidance. Everything earns its place, though the semicolon-heavy single block is denser than ideal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With annotations covering the safety profile, a 100% schema coverage, and an output schema for the return value, the description fills the remaining behavioral gaps (reversibility, timestamp, downstream effects, guidance). Nothing needed to invoke it correctly is missing.

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 3 is the baseline, but the description adds real invocation value by stating where mentionId comes from (list_mentions) and restating the status enum semantics. workspaceId is left entirely to the schema, so it does not fully compensate, but it exceeds the baseline.

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 ('Set one mention's triage status') and then defines exactly what each status means, including the distinct effects of APPROVED, REJECTED, and NEW. An agent can distinguish this from siblings like explain_mention or list_mentions immediately.

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?

Gives explicit operating guidance: judge on content and relevanceScore, call explain_mention first when the score looks off, and never approve an unread mention. It also names the concrete side effect that REJECTED drops the mention from default list_mentions and count_mentions results, with the workaround to pass statuses.

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

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