Skip to main content
Glama

billing

Manage billing tasks for MCP Analytics: check credit balance, view subscription status, or access the billing portal directly.

Instructions

Check credit balance, subscription status, or open billing portal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoBilling actionstatus

Implementation Reference

  • This request handler dynamically forwards any tool call (including 'billing') to the remote MCP server, as the tool catalog is fetched from the remote server at runtime.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      try {
        const result = await remoteClient.callTool({
          name: request.params.name,
          arguments: request.params.arguments || {},
        });
        return result;
      } catch (err) {
        return {
          content: [{ type: "text", text: `Error: ${err.message}` }],
          isError: true,
        };
      }
    });
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 fails to explain what 'portal' returns (URL vs redirect), whether 'usage' is read-only, side effects, or response formats. The agent cannot determine if 'portal' is destructive or requires special permissions.

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, front-loaded sentence of nine words with zero redundancy. Every word earns its place by describing a distinct capability of the tool.

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

Completeness3/5

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

For a simple single-parameter tool without output schema, the description adequately covers the available actions. However, it lacks information about return values (e.g., whether 'portal' returns a URL string) and doesn't clarify the difference between 'status' and 'usage' actions, leaving a small gap in completeness.

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?

With 100% schema coverage (parameter described as 'Billing action'), the baseline is 3. The description adds value by mapping the enum values to specific outcomes: 'status' checks subscription, 'portal' opens billing portal, and implies 'usage' handles credit balance checking. This semantic mapping helps the agent select the correct action value.

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?

The description clearly states three specific functions (checking credit balance, checking subscription status, opening billing portal) using distinct verbs. It clearly distinguishes this tool from siblings like datasets_list, reports_search, and connectors_query which handle data rather than account billing.

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?

While the description lists available actions, it provides no explicit guidance on when to prefer this over siblings (though the domain is distinct enough) or prerequisites like authentication requirements. It doesn't specify when to use 'status' vs 'usage' for checking balance information.

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/embeddedlayers/mcp-analytics'

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