Skip to main content
Glama
Sign In

Ava Advisor

by fund.ava
OverviewDiscussionsAdmin

List Portfolios

list_portfolios
Read-only

List the user's OWN portfolios (id, name, base_currency, account_type, nav, total_return_pct, unrealized_pnl, position_count, …) so you can pick one to analyze. Call this FIRST whenever the user says 'my portfolio' without a number — show the names, then pass the chosen id to portfolio_context. Owner-scoped: only ever the user's own portfolios. If count is 0 (they own none), the response carries a note with a create link — relay THAT (invite them to create a portfolio) instead of saying an empty 'you have no portfolios'.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true, and the description stays consistent while adding real behavioral context: strict owner scoping ('only ever the user's own portfolios') and the non-obvious empty-case behavior where `count` is 0 and the response carries a `note` with a create link. That last detail is exactly the kind of thing an agent could not infer from annotations or schema.

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?

Front-loaded with the action and purpose, then the usage routing rule, then the edge case — a sensible priority order with no filler sentences. The parenthetical field list is slightly dense but each field earns its place by telling the agent what to display.

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 and no parameters, the description carries the full burden and meets it: it lists return fields, states the ownership scope, specifies the follow-up tool call, and handles the zero-portfolio case. Nothing an agent needs to call and interpret this correctly is missing.

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 is 4; the description correctly adds no parameter noise. It does implicitly reveal response shape (including a `count` field) but nothing parameter-related is needed beyond that.

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 ('List the user's OWN portfolios') and enumerates the returned fields (id, name, base_currency, nav, position_count), so an agent knows exactly what comes back and can distinguish it from the sibling `portfolio_context`, which it explicitly names as the next step.

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 ('Call this FIRST whenever the user says "my portfolio" without a number'), names the alternative for the follow-up step (`portfolio_context` with the chosen id), and covers the unusual empty-result branch by telling the agent to relay the create link rather than saying 'you have no portfolios'.

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

All Ava Advisor 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