Skip to main content
Glama
Sign In

Returnolio

by com.returnolio
OverviewDiscussionsAdmin

Top 10 edition

get_top10_edition
Read-only

Get the latest Top 10 edition this plan may read, with a one-line thesis per company. The response names the edition it is: paid plans get the newest, the free plan gets the edition three months behind the newest published one. The response includes an app link to the full rationale for each company. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_top10_edition"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses the plan-based recency behavior and the three-month lag for free plans, which is genuine behavioral context an agent cannot get from structured fields. It also states that the response self-identifies which edition was returned and includes app links to fuller rationale. Minor waste in restating 'Read-only', which the annotation already covers.

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 tight sentences, front-loaded with the action and result, then the plan-gating rule, then the response contents. The closing 'Read-only.' is redundant against the readOnlyHint annotation and is the one sentence that does not earn its place.

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 carries the return-value burden and does so adequately: thesis lines, edition identity, and app links are all named. It leaves edge cases unaddressed, such as the list length, ordering, or what happens when no edition has been published yet.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly signals that selectivity is not caller-controlled but plan-controlled.

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?

States a specific verb and resource ('Get the latest Top 10 edition') plus the payload shape ('one-line thesis per company'), so the agent knows exactly what comes back. It does not explicitly contrast itself with the sibling get_top10 or get_top10_track_record, so differentiation is inferred rather than stated.

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 context is implied through the plan-tier explanation (paid plans get the newest edition, free plan gets the edition three months behind), which tells the agent what it will receive. However, it never says when to choose this over the sibling get_top10, which sits in the same catalog and is the obvious alternative.

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

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