Skip to main content
Glama
socialrouter

SocialRouter MCP Server

Official
by socialrouter

Get balance

get_balance

Check your SocialRouter credit balance to monitor remaining API usage.

Instructions

Check your SocialRouter credit balance

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'get_balance' tool handler: defines the tool registration with an empty input schema and a handler that calls client.getBalance() and returns a formatted balance string.
    server.registerTool(
      "get_balance",
      {
        title: "Get balance",
        description: "Check your SocialRouter credit balance",
        inputSchema: {},
      },
      async () => {
        const balance = await client.getBalance();
        return { content: [{ type: "text" as const, text: `Balance: $${balance.balance.toFixed(2)} ${balance.currency}` }] };
      }
    );
  • src/index.ts:59-70 (registration)
    The 'get_balance' tool is registered via server.registerTool at line 59.
    server.registerTool(
      "get_balance",
      {
        title: "Get balance",
        description: "Check your SocialRouter credit balance",
        inputSchema: {},
      },
      async () => {
        const balance = await client.getBalance();
        return { content: [{ type: "text" as const, text: `Balance: $${balance.balance.toFixed(2)} ${balance.currency}` }] };
      }
    );
  • Input schema for 'get_balance': empty object (no parameters), with title and description metadata.
    title: "Get balance",
    description: "Check your SocialRouter credit balance",
    inputSchema: {},
Behavior4/5

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

Despite no annotations, the description honestly indicates a read operation ('check'), but does not disclose return format or potential costs, though still adequate for a trivial tool.

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?

Single sentence with no unnecessary words; highly concise and front-loaded.

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

Completeness4/5

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

For a simple balance check with no parameters or output schema, the description provides sufficient context about the action and resource, though could hint at return format.

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?

No parameters exist, so schema coverage is 100%; baseline score of 3 applies as description adds no parameter info, but none is needed.

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

Purpose5/5

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

Clearly states the action ('check') and the resource ('SocialRouter credit balance'), and distinguishes from sibling tools which are about extraction and providers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs. alternatives, but the simple context and distinct sibling names imply its use case.

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/socialrouter/mcp'

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