Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

freeze_account

Temporarily suspend trading activity for a specific account to prevent unauthorized transactions or manage account access securely. Requires the account ID as input.

Instructions

Freeze a trading account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesAccount ID to freeze

Implementation Reference

  • Executes the freeze_account tool by sending a PUT request to the Paper Invest API endpoint `/accounts/${accountId}/freeze`.
    case 'freeze_account':
      response = await api.put(`/accounts/${args.accountId}/freeze`);
      break;
  • Defines the tool metadata including name, description, and input schema for 'freeze_account', which requires an 'accountId' string.
    {
      name: 'freeze_account',
      description: 'Freeze a trading account',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: { type: 'string', description: 'Account ID to freeze' }
        },
        required: ['accountId']
      }
    },
  • src/index.ts:388-392 (registration)
    Registers the list of tools (including freeze_account) with the MCP server via ListToolsRequestHandler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      };
    });
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Freeze' implies a significant mutation, but the description doesn't clarify what 'freeze' entails operationally (e.g., prevents trading, locks funds), whether it's reversible, requires specific permissions, or has side effects. This is inadequate for a mutation tool with zero 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 no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

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 complexity of a mutation tool ('freeze' implies significant account modification) with no annotations and no output schema, the description is incomplete. It lacks details on behavior, consequences, return values, or error conditions, leaving critical gaps for an agent to understand and use the tool safely.

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 input schema has 100% description coverage, with the 'accountId' parameter clearly documented. The description doesn't add any semantic details beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('freeze') and target resource ('a trading account'), providing a specific verb+resource combination. However, it doesn't differentiate this tool from potential alternatives like 'update_account' or 'reset_portfolio' among the sibling tools, which could also modify account states.

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. It doesn't mention prerequisites, exclusions, or compare it to sibling tools like 'update_account' or 'cancel_all_account_orders', leaving the agent without context for selection.

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