Skip to main content
Glama
enderekici

Trading 212 MCP Server

by enderekici

get_pie

Retrieve detailed information about a specific investment pie by its unique ID for portfolio analysis and management.

Instructions

Get detailed information about a specific pie by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pieIdYesThe unique identifier of the pie

Implementation Reference

  • The handler logic for the 'get_pie' tool, which extracts the pie ID from arguments, calls the client, and returns the response.
    case 'get_pie': {
      const { pieId } = PieIdInputSchema.parse(args);
      const pie = await client.getPie(pieId);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(pie, null, 2),
          },
        ],
      };
    }
  • The API client helper function that performs the actual network request to retrieve a specific pie by ID.
    async getPie(pieId: number): Promise<Pie> {
      return this.request(`/equity/pies/${pieId}`, {}, PieSchema);
    }
  • src/index.ts:301-313 (registration)
    The tool registration for 'get_pie' in the list of available tools.
      name: 'get_pie',
      description: 'Get detailed information about a specific pie by ID',
      inputSchema: {
        type: 'object',
        properties: {
          pieId: {
            type: 'number',
            description: 'The unique identifier of the pie',
          },
        },
        required: ['pieId'],
      },
    },
Behavior2/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 of behavioral disclosure. It states this is a 'Get' operation, implying it's likely read-only, but doesn't confirm if it's safe, requires authentication, has rate limits, or what the output format might be. This leaves significant gaps for a tool with no structured safety hints.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It's front-loaded and appropriately sized for a simple retrieval tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, potential error cases, or behavioral traits like idempotency. For a retrieval tool in a financial context (inferred from siblings), more context on data sensitivity or response structure would be helpful.

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 schema description coverage is 100%, with the parameter 'pieId' clearly documented as 'The unique identifier of the pie'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for high schema coverage without extra value.

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?

The description clearly states the verb ('Get') and resource ('detailed information about a specific pie'), making the purpose understandable. However, it doesn't distinguish this from sibling tools like 'get_pies' (plural) or 'get_portfolio', which might also retrieve pie-related information, so it misses full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. For example, it doesn't specify if this should be used instead of 'get_pies' for single pies or 'get_portfolio' for broader data, leaving the agent to infer usage from context alone.

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/enderekici/trading212-mcp'

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