Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

update_account

Modify account details, such as updating the name or other information, using the specified account ID on the Paper MCP Server. Simplify account management through natural language interactions.

Instructions

Update account details

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesAccount ID
nameNoNew account name

Implementation Reference

  • Handler function for 'update_account' tool that performs a PUT request to update the account name via the Paper Invest API.
    case 'update_account':
      response = await api.put(`/accounts/${args.accountId}`, {
        name: args.name
      });
      break;
  • Tool definition including name, description, and input schema for the 'update_account' tool, used for registration in listTools.
    {
      name: 'update_account',
      description: 'Update account details',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: { type: 'string', description: 'Account ID' },
          name: { type: 'string', description: 'New account name' }
        },
        required: ['accountId']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a mutation operation but doesn't disclose critical details like whether changes are reversible, what permissions are required, how errors are handled, or what the response contains. This leaves significant gaps for an agent to understand the tool's behavior.

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

Conciseness4/5

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

The description is extremely concise at three words, which is efficient and front-loaded. However, it borders on under-specification given the tool's mutation nature and lack of annotations, slightly reducing its effectiveness despite the brevity.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address behavioral aspects like side effects, error conditions, or return values, which are crucial for safe and effective use. The context demands more detail than provided.

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 both parameters clearly documented in the schema (accountId and name). The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. The baseline score of 3 reflects adequate but minimal value added by the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Update account details' clearly states the action (update) and target resource (account), but it's vague about what specific details can be updated. It doesn't distinguish this tool from potential siblings like 'freeze_account' or 'upgrade_to_margin' that 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?

No guidance is provided about when to use this tool versus alternatives. For example, it doesn't mention whether this is for basic profile updates versus more specialized account modifications handled by other tools, nor does it specify prerequisites like account ownership or permissions.

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