Skip to main content
Glama

Get Stock Token portfolio

get_portfolio
Read-only

Retrieve any wallet’s multiplier-correct stock token portfolio on Robinhood Chain, including token balances, ERC-8056 share equivalents, USD value, and USDG cash balance.

Instructions

Multiplier-correct Stock Token portfolio for any address: per-position token balance, ERC-8056 share-equivalent, USD value, plus the USDG cash balance. Read-only.

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": {
      "address": "<address>"
    },
    "name": "get_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesWallet address (0x…40 hex) to value.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so "Read-only" is largely redundant confirmation rather than new information. The genuinely additive behavior detail is "Multiplier-correct" and the ERC-8056 share-equivalent framing, which explains how values are computed; nothing is said about handling of invalid/EOA addresses, unsupported tokens, or chain scope.

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?

One front-loaded sentence with the resource and the returned fields, no filler. The density of domain jargon (ERC-8056, USDG, multiplier-correct) is efficient for a domain-aware agent but slightly compresses the value.

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 by naming the four result components (token balance, share-equivalent, USD value, USDG cash). Missing pieces are error/empty behavior and chain context, but for a one-parameter read-only tool this is close to complete.

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 address parameter is documented in-schema as 0x…40 hex. The description only restates "for any address" without adding format, chain, or validation semantics, so the schema does the work — baseline 3.

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+resource (retrieve a Stock Token portfolio for an address) and enumerates what the result contains: per-position balance, ERC-8056 share-equivalent, USD value, USDG cash. That is far more concrete than the sibling names (get_stock_quote, list_stock_tokens), though it never explicitly contrasts itself with them.

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?

"For any address" implies the input scope and the description implies a valuation use case, but there is no explicit when-to-use statement, no exclusions, and no pointer to an alternative for single-token quotes or token lists. Usage must be inferred from the purpose.

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