Skip to main content
Glama

Get a public portfolio

get_portfolio
Read-onlyIdempotent

Use this only when the user names a Telegram @username and wants the gifts that profile publicly shows on its GiftChecker page (/u/): counts, the valuation in Stars and up to 20 numbered gifts. Users who hid their page or are not known answer not_found. Never returns wallets or balances. Do not use it to search for people or to list portfolios.

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

Input Schema

NameRequiredDescriptionDefault
usernameYesTelegram @username, with or without the @.

Output Schema

NameRequiredDescriptionDefault
urlYes
noteYes
giftsYes
priceNo
usernameYes
collectionsNo
observed_atNo
display_nameNo
regular_giftsNo
numbered_giftsNo
valuation_starsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them by disclosing the not_found outcome for hidden or unknown profiles, the 20-gift cap, and the hard boundary that wallets and balances are never returned. These are exactly the behavioral facts an agent needs before committing to the call.

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

Conciseness5/5

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

Three short sentences, front-loaded with the gating condition, then the return shape, then the exclusion boundary. No filler and no repetition of schema or annotation content.

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?

An output schema exists so return values need no prose explanation, yet the description still summarizes the payload and failure mode. For a one-parameter read tool with full annotation coverage, nothing an agent needs is missing.

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?

The single parameter is fully documented in the schema (100% coverage, including the optional @ prefix), so the schema already carries the load. The description adds only the framing that the username identifies a Telegram profile with a public page; useful but marginal beyond structured data, so 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 ('get' the 'public portfolio' a Telegram profile shows on its GiftChecker page) and pinpoints the content (counts, Stars valuation, up to 20 numbered gifts). That is enough to distinguish it from siblings like get_collection or search 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('only when the user names a Telegram @username') and explicit exclusions ('Do not use it to search for people or to list portfolios'), which routes the agent away from search and listing tools. Both the when and the when-not conditions are stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources