Skip to main content
Glama

Create account and API key

get_account

Get an account and an API key. Requires an email address. The key is returned ONCE and cannot be shown again — store it immediately. Beta quotas are low by design; they are hard stops, never overage billing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "email": "<email>"
    },
    "name": "get_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYes
trafficNoOptional. What your agent sends.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that the API key is returned ONCE, cannot be shown again, and must be stored immediately, plus that beta quotas are hard stops with no overage billing. These are operationally critical facts an agent cannot infer from readOnlyHint/idempotentHint. It stops short of stating error behavior or what happens on a repeat call for the same email.

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?

Three tight sentences, with the irreversible key-return warning front-loaded right after the core statement. No redundant or filler wording, though the opening sentence is the vaguest part and leads with weaker information.

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 non-idempotent provisioning call with no output schema, the description covers the most dangerous gotcha (one-time key exposure) and quota limits, but leaves the actual effect unclear (account creation vs lookup) and says nothing about repeated calls or failure modes.

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 coverage is 50% and the description only restates that email is required, which the schema already encodes. The optional 'traffic' parameter is never mentioned in the description, so it adds no interpretive value for that half of the input surface.

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 says 'Get an account and an API key', which reads like a retrieval operation, yet the annotations mark it non-read-only and the title says 'Create account and API key'. The resource is identifiable (account + API key) but the verb is ambiguous and never resolves the create-vs-get tension, so an agent cannot be fully sure this is a registration call that provisions something new.

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?

There is no statement of when to call this versus siblings such as issue_pass or list_packages, and no prerequisites beyond 'Requires an email address'. The beta-quota note is environmental context, not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.