Skip to main content
Glama
Sign In

Returnolio

by com.returnolio
OverviewDiscussionsAdmin

Moonshot Detected companies

get_moonshot
Read-only

Get the Moonshot Detected companies, the momentum picks inside Returnolio's monthly Top 10, from the newest edition your plan can open. Paid plans get the newest edition; the free plan gets the edition three months behind it, and the response names the edition it is. The response includes an app link to the full list. 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_moonshot"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the trailing 'Read-only' merely repeats that, earning no credit. The description does add genuinely non-obvious behavior: plan-dependent edition gating, a three-month lag for free plans, and that the response self-identifies its edition, which an agent needs to interpret results.

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 sentences, front-loaded with the resource and its parent context, then the access rule, then the response shape. The only real waste is the closing 'Read-only' sentence, which duplicates the readOnlyHint annotation.

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?

There is no output schema, and the description compensates by naming two response elements (the edition identifier and an app link to the full list). For a zero-parameter read tool, that plus the access rules is nearly everything an agent needs; field-level detail of the company entries is the only remaining gap.

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; the baseline applies. The plan-based selection being automatic rather than parameterized is worth the note it gets.

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 ('Get the Moonshot Detected companies') and immediately scopes it as 'the momentum picks inside Returnolio's monthly Top 10', which cleanly separates it from the sibling get_top10 and get_top10_edition. An agent can pick between these without opening a 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?

Explains the effective context of use through plan-based edition selection (paid = newest, free = three months behind), which tells the agent what it will actually get. It does not explicitly say when to prefer this over get_top10, but the 'momentum picks inside Top 10' framing implies the narrower subset well enough.

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