Skip to main content
Glama

issue_api_key

Read-onlyIdempotent

Get the link to create a ThinAir GEO (geocoding/routing) API key. Returns console_url (the signed-in ThinAir Geo console) and instructions; it does NOT return a key and does not create, rotate or revoke any key. The owner signs in, creates the key there and sees it once in their own browser, then sends it as an Authorization: Bearer header. Existing keys keep working. Counts as 1 query against your daily quota. NOTE: keys created there work ONLY against ThinAir Geo — they do NOT authenticate against ThinAir Data, which issues its own ta_data_* keys from its own identically-named tool.

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": "issue_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
planNo
errorNo
statusYes
console_urlNoLink to the signed-in ThinAir Geo console, where the owner creates an API key and sees it once in their own browser. This tool never returns a key.
instructionsNoHow to create the key in the console and send it (Authorization: Bearer). Surface to the user as written.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
  2. Changed9 schema fields changed
    • removedOutput schema / properties / api_key
      Removed value: -{
      -  "description": "One-time API key secret. Returned only on successful creation, in both structuredContent.api_key and content[0].text. Save this key now. It is shown once. ThinAir authenticates using a hash of the key. Matches AWS IAM / Stripe / GitHub PAT one-time-reveal semantics.",
      -  "type": "string"
      -}
    • addedOutput schema / properties / console_url
      Added value: +{
      +  "description": "Link to the signed-in ThinAir Geo console, where the owner creates an API key and sees it once in their own browser. This tool never returns a key.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / credential_returned_once
      Removed value: -{
      -  "type": "boolean"
      -}
    • addedOutput schema / properties / instructions
      Added value: +{
      +  "description": "How to create the key in the console and send it (Authorization: Bearer). Surface to the user as written.",
      +  "type": "string"
      +}
    • removedOutput schema / properties / key_id
      Removed value: -{
      -  "description": "Non-secret fingerprint of the issued key. Safe to log and surface in UI.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / previous_keys_retire_at
      Removed value: -{
      -  "description": "ISO 8601 instant when the previous keys stop working (one hour after this mint). Present only when previous_keys_retiring > 0. Update anything still using them before this time.",
      -  "type": "string"
      -}
    • removedOutput schema / properties / previous_keys_retiring
      Removed value: -{
      -  "description": "How many previously-live keys this mint scheduled to retire. issue_api_key rotates: after the grace window the returned key is the only live key on the account. 0 means there was nothing else.",
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • removedOutput schema / properties / usage
      Removed value: -{
      -  "type": "string"
      -}
    • removedOutput schema / properties / user
      Removed value: -{
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • changedOutput schema / properties / api_key / description
      Previous value: -"One-time API key secret. Returned only on successful creation, in both structuredContent.api_key and content[0].text — save it immediately. The server stores only sha-256 of the secret; once this response is lost, the key is unrecoverable and must be rotated. Matches AWS IAM / Stripe / GitHub PAT one-time-reveal semantics."New value: +"One-time API key secret. Returned only on successful creation, in both structuredContent.api_key and content[0].text. Save this key now. It is shown once. ThinAir authenticates using a hash of the key. Matches AWS IAM / Stripe / GitHub PAT one-time-reveal semantics."
  4. Changed2 schema fields changed
    • addedOutput schema / properties / previous_keys_retire_at
      Added value: +{
      +  "description": "ISO 8601 instant when the previous keys stop working (one hour after this mint). Present only when previous_keys_retiring > 0. Update anything still using them before this time.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / previous_keys_retiring
      Added value: +{
      +  "description": "How many previously-live keys this mint scheduled to retire. issue_api_key rotates: after the grace window the returned key is the only live key on the account. 0 means there was nothing else.",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  5. Changed2 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • changedOutput schema / properties / api_key / description
      Previous value: -"One-time API key secret. Returned only on successful creation. Treat as a credential — never log, echo, or render in text channels."New value: +"One-time API key secret. Returned only on successful creation, in both structuredContent.api_key and content[0].text — save it immediately. The server stores only sha-256 of the secret; once this response is lost, the key is unrecoverable and must be rotated. Matches AWS IAM / Stripe / GitHub PAT one-time-reveal semantics."
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "api_key": {
      +      "description": "One-time API key secret. Returned only on successful creation. Treat as a credential — never log, echo, or render in text channels.",
      +      "type": "string"
      +    },
      +    "credential_returned_once": {
      +      "type": "boolean"
      +    },
      +    "error": {
      +      "additionalProperties": false,
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "code",
      +        "message"
      +      ],
      +      "type": "object"
      +    },
      +    "key_id": {
      +      "description": "Non-secret fingerprint of the issued key. Safe to log and surface in UI.",
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "plan": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "enum": [
      +        "success",
      +        "error"
      +      ],
      +      "type": "string"
      +    },
      +    "usage": {
      +      "type": "string"
      +    },
      +    "user": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent and non-destructive, and the description adds real behavior beyond them: it returns only console_url plus instructions, the key is visible once in the owner's own browser, existing keys keep working, and the call costs 1 query against the daily quota. The scope caveat about Geo vs Data authentication is exactly the kind of cross-service constraint an agent could not infer.

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?

Front-loaded with what the tool returns, then the negative scope, then operational caveats (Bearer header, quota, Geo-only). Every sentence carries information, though the quota and header sentences could be folded tighter without loss.

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?

An output schema exists, yet the description still names the meaningful return (console_url and instructions), which prevents an agent from expecting a key back. For a zero-parameter, read-only, one-purpose tool, 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?

There are no parameters at all, so the baseline is 4 and there is nothing the description could add. It correctly signals that the call is argument-free by describing it purely as a link fetch.

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 precise verb+resource (get the link to create a ThinAir GEO API key) and immediately bounds it negatively: it does not return a key and does not create, rotate or revoke one. That contrast distinguishes it from anything that actually manages credentials.

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

Usage Guidelines5/5

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

Explains the flow that selects this tool (owner signs in, creates the key in the console, sends it as a Bearer header) and explicitly names the confusing alternative — ThinAir Data's identically-named tool — with the condition that Geo keys do not authenticate against Data. Exclusion guidance is explicit.

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