Skip to main content
Glama
Sign In

Returnolio

by com.returnolio
OverviewDiscussionsAdmin

My portfolio (read-only)

my_portfolio
Read-only

Get the signed-in user's own Returnolio portfolio: holdings aggregated with weighted-average cost basis (split-adjusted), each with shares, cost basis and Returnolio score, plus total cost. No prices, market value or profit/loss; those are in the app. This is a mechanical numbers-only readout, NOT analysis, a rating, or investment advice. To edit holdings, the user does it in the app. The response includes an app link to the portfolio.

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": "my_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond readOnlyHint=true, it discloses what the numbers are (split-adjusted weighted-average cost basis) and, unusually, what is deliberately absent (prices, market value, profit/loss) plus the app-link behavior. It also sets a firm expectation that this is not analysis or advice, though it says nothing about response size or latency.

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?

Payload summary is front-loaded and the caveats follow in a logical order. The 'NOT analysis, a rating, or investment advice' plus 'mechanical numbers-only readout' clauses overlap somewhat, costing a little tightness.

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 no output schema, the description carries the return-value burden and does so: it names every field category, notes the app link in the response, and flags missing fields so the agent can explain them. Nothing needed to call or interpret this tool is absent.

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 the baseline applies; the description correctly implies no inputs are needed by framing it as the signed-in user's own data. There is nothing further to add on parameter meaning.

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 signed-in user's own Returnolio portfolio') and enumerates the payload (holdings, split-adjusted weighted-average cost basis, shares, Returnolio score, total cost). This clearly separates it from siblings like get_portfolio_snapshot and my_watchlist.

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?

Makes the scoping explicit: the signed-in user's own portfolio only, and it redirects edits to the app. It does not name an alternative tool or say when a different portfolio-related sibling would be preferable, so it stops short of full routing guidance.

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