Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

get_account

Retrieve account details by providing the account ID on the Paper MCP Server, enabling AI assistants to access and manage trading platform data through natural language interactions.

Instructions

Get account details by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesAccount ID

Implementation Reference

  • Handler implementation for the 'get_account' tool. Makes a GET request to the API endpoint `/accounts/{accountId}` to fetch account details.
    case 'get_account':
      response = await api.get(`/accounts/${args.accountId}`);
      break;
  • Tool definition including name, description, and input schema for 'get_account'. Used for tool discovery and validation.
      name: 'get_account',
      description: 'Get account details by ID',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: { type: 'string', description: 'Account ID' }
        },
        required: ['accountId']
      }
    },
Behavior2/5

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

With no annotations, the description carries full burden but only states it retrieves details by ID. It lacks behavioral context such as whether this is a read-only operation (implied but not stated), authentication needs, rate limits, error conditions, or what 'details' includes (e.g., balance, status). This is inadequate for a tool with no annotation coverage.

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 with zero waste—it directly states the tool's purpose without unnecessary words, making it appropriately sized and front-loaded for clarity.

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 no annotations, no output schema, and a simple parameter (100% coverage), the description is minimal. It lacks completeness by not explaining what 'account details' includes, potential return formats, or any behavioral traits, which is insufficient for guiding an agent effectively in this context.

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 description coverage is 100%, with the single parameter 'accountId' documented in the schema. The description adds no additional meaning beyond implying ID-based lookup, so it meets the baseline of 3 where the schema does the heavy lifting without extra value from the description.

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 ('account details'), specifying retrieval by ID. It distinguishes from siblings like 'update_account' (mutation) and 'get_account_orders' (different resource), though it doesn't explicitly contrast with 'get_account_portfolios' or 'freeze_account'.

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't specify if this is for basic account info versus using 'get_account_orders' for order details or 'update_account' for modifications, 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

Related 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/paperinvest/mcp-server'

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