Skip to main content
Glama

Get an API key for your user

start_signup

Starts getting a free API key. Say what data your user wants and what they want to do with it; ask them if you do not know, and do not guess. Returns a link for your user to approve in the browser. Show them the link and code, then call finish_signup.

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": {
      "data_wanted": "<data_wanted>",
      "use_case": "<use_case>"
    },
    "name": "start_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentNoYour agent or client name.
detailsNoAny other fields worth telling us, with any names you like, for example language, schedule or team_size. Up to 20.
found_usNoOptional. How your user says they found this API, in their words, for example a web search or a recommendation. Ask once. If they do not say, leave it out: never guess or fill in a placeholder. Up to 300 characters.
use_caseYesWhat they want to do with it. 3 to 1000 characters.
data_wantedYesWhat data they are looking for: leagues, stats, tiers, history, refresh speed. 3 to 1000 characters.
agent_found_usNoOptional. How you, the agent, found this API. Kept apart from found_us. Up to 300 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, non-idempotent, non-destructive), the description discloses the key behavioral trait: this is an interactive, out-of-band approval flow that returns a link and code the user must open in a browser, and the operation is only half-finished until finish_signup is called. It does not clarify what happens on repeated calls or whether pending signups expire, which is why it falls short of a 5.

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?

Four short sentences, front-loaded with the purpose and followed by the procedural steps and the handoff to finish_signup. No redundant restatement of the schema fields, and every sentence carries an actionable instruction.

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?

With no output schema, the description correctly takes on the burden of describing the return value (a browser link plus a code) and the follow-up tool. For a six-parameter, multi-step signup flow it is nearly complete, missing only edge-case behavior such as re-invocation or abandoned signups.

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?

Schema coverage is 100%, so baseline would be 3, but the description adds real semantic weight to the two required parameters: data_wanted and use_case must reflect what the user actually said, and the agent must ask rather than invent values. That is a usage constraint the schema does not encode.

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 first sentence names a specific action and outcome ('Starts getting a free API key'), and the description immediately positions it in a two-step flow by telling the agent to call finish_signup afterward. That lets an agent distinguish it from the sibling finish_signup and from other setup tools without opening a schema.

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

Usage Guidelines4/5

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

It gives clear procedural guidance: gather the user's data and use case, ask rather than guess, show the returned link and code, then call finish_signup. The gap is that it never says when NOT to use it — for example how it relates to the sibling complete_setup, or what to do if the user already has a key.

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.

Resources