Skip to main content
Glama
modellers

ConsignCloud MCP Server

by modellers

get_account

Retrieve account details by ID to manage consignment business operations, including vendor information and sales tracking.

Instructions

Get details of a specific account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAccount ID

Implementation Reference

  • Core implementation of getAccount: makes HTTP GET to /accounts/{id} and converts the API response to typed Account.
    async getAccount(id: string): Promise<Account> {
      const response = await this.client.get(`/accounts/${id}`);
      return this.convertAccountResponse(response.data);
    }
  • src/server.ts:148-158 (registration)
    MCP tool registration defining the 'get_account' tool, its description, and input schema.
    {
      name: 'get_account',
      description: 'Get details of a specific account',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Account ID' },
        },
        required: ['id'],
      },
    },
  • Server-side tool execution handler that dispatches to client.getAccount and formats response as MCP content.
    case 'get_account':
      return { content: [{ type: 'text', text: JSON.stringify(await client.getAccount((args as any).id), null, 2) }] };
  • TypeScript interface defining the Account output type returned by getAccount.
    export interface Account {
      id: string;
      number: string;
      first_name: string | null;
      last_name: string | null;
      company: string | null;
      email: string | null;
      phone_number: string | null;
      balance: number; // converted to store currency
      default_split: number;
      default_inventory_type: 'consignment' | 'buy_outright' | 'retail';
      is_vendor: boolean;
      created: string;
    }
  • Helper function to convert raw API account response (with cents) to typed Account with store currency.
    private convertAccountResponse(account: any): Account {
      return {
        ...account,
        balance: this.convertFromApiCents(account.balance),
      };
    }
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 read-only behavior, but doesn't clarify permissions, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency.

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, clear sentence with zero wasted words. It's appropriately sized and front-loaded, directly stating the tool's purpose without unnecessary elaboration, making it highly efficient.

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 'details' are returned, potential errors, or behavioral traits like idempotency. For a read operation with no structured support, more context is needed to fully guide the agent.

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 'id' parameter documented as 'Account ID'. The description adds no additional meaning beyond this, such as format examples or sourcing guidance. With high schema coverage, the baseline score of 3 is appropriate as the schema handles 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 verb ('Get') and resource ('details of a specific account'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_account_stats' or 'list_accounts', which would require more specific language about what details are retrieved versus aggregated statistics or multiple accounts.

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 siblings like 'list_accounts' for multiple accounts or 'get_account_stats' for aggregated data, nor does it specify prerequisites such as needing an account ID. This leaves the agent without contextual usage cues.

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/modellers/mcp-consigncloud'

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