Skip to main content
Glama

Get a free developer key (free)

get_free_key

Get a free developer key for the metered tools on this server, without leaving this session. No payment, no account, no card. The key holds a small daily allowance that refills every day, and one credit is consumed per verdict, nothing on an error. Present it as the X-API-Key header on this MCP connection, or hand it to whoever configures your client. Throttled exactly as the equivalent HTTP endpoint is: one key per source per window, so calling this again shortly after will be refused rather than minting a second key. Store the key when you get it: it is shown once and cannot be recovered.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_free_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tierNo
errorNoPresent instead of a key when one could not be minted right now.
api_keyNoShown once. Store it before doing anything else.
creditsNo
daily_limitNoScans per day, refilled daily.
retry_after_hoursNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: no payment/account/card, daily refilling allowance, one credit per verdict with no charge on errors, exact throttle semantics (one key per source per window), how to present the key (X-API-Key header), and the critical one-shot disclosure — the key is shown once and cannot be recovered. This is a mutation-free but non-idempotent mint operation fully explained.

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 sentences, front-loaded with the purpose, then cost, then credential handling, then throttling and the one-time-display warning. No sentence is filler — the ordering puts the operational risk (store the key now) where an agent will read it.

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

Completeness5/5

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

With an output schema present, return-value shape needn't be described, and the description still covers everything an agent needs: no args, no auth required, cost model, transport of the credential, throttle behavior, and irreversibility of the secret. Nothing material is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly communicates that the call takes no arguments and returns the key inline in the session.

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?

States a specific verb+resource (get a free developer key) and scopes it to 'the metered tools on this server, without leaving this session.' This is unmistakably distinct from every sibling, which are all scan/verify/lookup tools.

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?

Explains the condition for use (need a key for metered tools) and gives an implicit 'when not to': calling again shortly after will be refused by the one-key-per-source-window throttle. No named alternative tool exists, so nothing further is needed, but it doesn't explicitly frame the refusal path as 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.