Skip to main content
Glama
Sign In

Returnolio

by com.returnolio
OverviewDiscussionsAdmin

Open in Returnolio app

get_app_link
Read-only

Return the exact Returnolio app link for an action this read-only connector cannot perform (anything that places trades, changes holdings or watchlists, manages alert subscriptions, or asks for personalized advice). Use this whenever the user wants to DO something the connector cannot do: it says the connector is read-only and gives the precise link, including a note to open it in a browser if it is not clickable.

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": {
      "action": "<action>"
    },
    "name": "get_app_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesWhat the user wants to do, e.g. 'buy a stock', 'edit my portfolio', 'set an alert', 'see the Top 10', 'see IPOs'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true; the description goes further by making clear it does not perform the action, only returns a link, and by disclosing that the response includes a note about opening the link in a browser if it is not clickable. It does not say what happens when the supplied action matches none of the listed categories, which keeps it short of a 5.

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

Conciseness3/5

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

The core rule is front-loaded, but the second sentence largely restates the first ('Use this whenever the user wants to DO something the connector cannot do' repeats 'an action this read-only connector cannot perform'). Only the browser-clickability note is genuinely new information in that sentence.

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 one-parameter tool with no output schema, the description covers what comes back (a precise link with an accompanying note) and why the tool exists. The only gap is undefined behavior for an action outside the enumerated categories.

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% and the single 'action' parameter already carries a description with concrete examples ('buy a stock', 'set an alert', 'see the Top 10'). The description adds no format, granularity, or phrasing guidance beyond the schema, so the baseline 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?

States a specific verb and resource ('Return the exact Returnolio app link') plus an explicit scope: actions this read-only connector cannot perform. It then enumerates those action families (trades, holdings/watchlists, alert subscriptions, personalized advice), which cleanly separates it from the data-retrieval siblings like get_top10 or my_portfolio.

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 an explicit trigger rule ('Use this whenever the user wants to DO something the connector cannot do') and names the categories that qualify. An agent does not need to infer when to route here versus to a data tool.

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