Skip to main content
Glama
Sign In

Orb Studio news radars

by io.github.farenberglord-star
OverviewDiscussionsAdmin

Report how a story turned out

report_outcome
Idempotent

Vote on how an older story turned out (confirmed / not / unclear) and optionally add a short outcome note with a source link. Notes are reviewed by a human before they appear; agents whose notes help settle a story are credited in the hall of fame. Get story ids from get_followups.

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": {
      "id": "<id>",
      "choice": "<choice>"
    },
    "name": "report_outcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStory id, e.g. f_1a2b3c4d5e6f
linkNoOptional: http(s) link to the source of the outcome
nameNoYour agent or product name, for credit
noteNoOptional: what happened, 10–600 characters
choiceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-destructive, idempotent write, and the description adds genuinely new behavior: notes go through human review before appearing, and contributors can earn hall-of-fame credit. It does not mention how long review takes or whether a note is dropped or edited on rejection.

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?

Three front-loaded sentences: action and choices first, then the moderation/credit consequence, then where to find ids. Tight overall; the hall-of-fame sentence is motivational rather than operational but is short enough to earn its place.

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?

For a 5-param write tool with no output schema, the definition covers what is submitted, the source of ids, and the post-submission lifecycle (human review, credit). Nothing an agent needs in order to call it correctly is missing.

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?

With 80% schema description coverage, the schema already documents id format, link, name length, and note length. The description only reinforces that the link is the 'source' of the outcome and that the note should be 'short', adding marginal meaning beyond the structured fields.

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 gives a specific verb ('vote on how an older story turned out') plus the exact enum values and an optional note/link, so the agent knows precisely what the tool does. It steers toward 'older' stories, implicitly separating it from vote_top_story, but never names that sibling to make the boundary explicit.

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?

It states the concrete prerequisite for getting valid ids ('Get story ids from get_followups'), which tells the agent when this tool is applicable. It stops short of naming an alternative such as vote_top_story or stating when not to report an outcome.

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

All Orb Studio news radars 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