Skip to main content
Glama

get_account

Read-onlyIdempotent

Retrieve your BubblyPhone account details including name, email, company, and balance to verify billing and manage voice agent settings.

Instructions

Get your BubblyPhone account information including name, email, company, and balance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for get_account tool - an async arrow function that calls client.get("/auth/me") via the callTool wrapper to fetch account information from the API.
    async () => callTool(() => client.get("/auth/me"))
  • The callTool helper function that wraps the API call with error handling. It executes the provided function and formats the result or catches API errors.
    async function callTool<T>(fn: () => Promise<T>) {
      try {
        return toolResult(await fn());
      } catch (err) {
        const apiErr = err as ApiError;
        return toolError(`API error (${apiErr.status}): ${apiErr.message}`);
      }
    }
  • The registerAccountTools function that registers the get_account tool with the MCP server, including its name, schema definition, and handler.
    export function registerAccountTools(server: McpServer, client: BubblyPhoneClient) {
      server.registerTool(
        "get_account",
        {
          description: "Get your BubblyPhone account information including name, email, company, and balance.",
          inputSchema: {},
          annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
        },
        async () => callTool(() => client.get("/auth/me"))
      );
  • The schema definition for the get_account tool - includes description, empty inputSchema (no parameters required), and behavior annotations indicating it's read-only, non-destructive, idempotent, and closed-world.
    {
      description: "Get your BubblyPhone account information including name, email, company, and balance.",
      inputSchema: {},
      annotations: { readOnlyHint: true, destructiveHint: false, idempotentHint: true, openWorldHint: false },
    },
  • src/server.ts:25-25 (registration)
    The server-level registration where registerAccountTools is called to attach the get_account tool to the MCP server instance.
    registerAccountTools(server, client);
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds value by specifying what data is returned (name, email, company, balance) since no output schema exists, but does not disclose additional behavioral traits like rate limits, authentication scope, or caching behavior.

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 front-loads the action and resource, then appends the specific field list, earning its place with high information density.

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

Completeness5/5

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

Given that no output schema exists, the description compensates appropriately by enumerating the returned fields (name, email, company, balance). Combined with comprehensive annotations covering safety profiles and the trivial parameter schema, the description provides complete context for invoking this simple read-only tool.

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 input schema has zero parameters. According to the scoring guidelines, 0 parameters establishes a baseline score of 4, as there are no parameter semantics to clarify beyond what the empty schema already communicates.

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 (BubblyPhone account information) and lists specific return fields (name, email, company, balance). However, it does not explicitly distinguish from the sibling tool 'get_balance', which also returns balance information, potentially causing confusion about which to use.

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 like 'get_balance'. It lacks prerequisites, conditions, or explicit comparisons to sibling tools that would help an agent select the correct tool for balance-checking scenarios.

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

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