Skip to main content
Glama

t2000_portfolio

Display investment portfolio details including positions, cost basis, current value, and P&L metrics to monitor performance and strategy groupings.

Instructions

Show investment portfolio — positions, cost basis, current value, unrealized/realized P&L, strategy groupings. For a full account snapshot, prefer t2000_overview instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the `t2000_portfolio` tool which fetches the agent's portfolio, performs some minor enrichment on position data, and returns it as a stringified JSON object.
    server.tool(
      't2000_portfolio',
      'Show investment portfolio — positions, cost basis, current value, unrealized/realized P&L, strategy groupings. For a full account snapshot, prefer t2000_overview instead.',
      {},
      async () => {
        try {
          const result = await agent.getPortfolio();
          const enriched = {
            ...result,
            positions: result.positions.map(p => ({
              ...p,
              ...(p.currentPrice === 0 && p.totalAmount > 0 ? { note: 'price unavailable' } : {}),
            })),
          };
          return { content: [{ type: 'text', text: JSON.stringify(enriched) }] };
        } catch (err) {
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies this is a read-only operation ('Show'), but doesn't explicitly state permissions, rate limits, or error conditions. It adds some context by specifying the data fields returned, but lacks details on behavioral traits like response format or potential side effects.

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?

The description is highly concise and well-structured: two sentences that efficiently convey the tool's purpose and usage guidelines without any wasted words. Every sentence adds value, making it easy for an agent to parse and understand.

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?

Given the tool has 0 parameters, no annotations, and no output schema, the description is reasonably complete. It explains what the tool does and when to use it, but could be more comprehensive by detailing the return format or any behavioral constraints. However, for a simple read operation, it provides sufficient context for an agent to invoke it correctly.

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 has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't mention parameters, which is appropriate. A baseline of 4 is applied as it compensates adequately for the lack of parameters by focusing on the tool's purpose and usage.

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?

The description clearly states the tool's purpose with specific details: 'Show investment portfolio — positions, cost basis, current value, unrealized/realized P&L, strategy groupings.' It uses a precise verb ('Show') and resource ('investment portfolio') while distinguishing it from the sibling tool t2000_overview by specifying what data is included.

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?

The description provides explicit guidance on when to use this tool versus alternatives: 'For a full account snapshot, prefer t2000_overview instead.' This clearly indicates that t2000_portfolio is for portfolio-specific details, while t2000_overview is for a broader account overview, helping the agent choose appropriately.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mission69b/t2000'

If you have feedback or need assistance with the MCP directory API, please join our Discord server