Skip to main content
Glama

Show my key and quota

get_api_key
Read-onlyIdempotent

Show my key, tier and remaining quota

Who am I and how much quota is left. Works without a key too (then it describes the anonymous allowance for your IP).

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_api_key"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
tierNo
labelNo
quotaNo
key_idNo
call_idNo
doc_notesNo
email_verifiedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedOutput schema / properties / quota / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "limit": {
      -        "anyOf": [
      -          {
      -            "description": "Calls allowed per window.",
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ],
      -        "description": "Calls allowed per window."
      -      },
      -      "remaining": {
      -        "anyOf": [
      -          {
      -            "type": "integer"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      },
      -      "resets_at": {
      -        "type": [
      -          "string",
      -          "null"
      -        ]
      -      },
      -      "window": {
      -        "anyOf": [
      -          {
      -            "enum": [
      -              "hour",
      -              "day"
      -            ],
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "limit": {
      +        "anyOf": [
      +          {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "description": "Calls allowed per window."
      +      },
      +      "remaining": {
      +        "anyOf": [
      +          {
      +            "maximum": 9007199254740991,
      +            "minimum": -9007199254740991,
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      },
      +      "resets_at": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "window": {
      +        "anyOf": [
      +          {
      +            "enum": [
      +              "hour",
      +              "day"
      +            ],
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description earns credit for going further: it discloses that the call succeeds without a key and that in that case the result describes the anonymous per-IP allowance. That is a real behavioral trait an agent could not infer from the structured fields; what it does not add is any note on whether calling it affects or refreshes the key itself.

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 the core output list, then a second line for the anonymous fallback. The material is slightly restated three times (title, first line, and 'Who am I and how much quota is left'), which costs a bit of density but not clarity.

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?

A no-parameter, read-only introspection tool with rich annotations and an output schema, so return values need no prose. The description covers the one non-obvious case (anonymous/IPS allowance) an agent would otherwise get wrong.

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 the baseline of 4 applies and there is no parameter semantics burden to carry.

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 and resource ('show my key, tier and remaining quota') and the second line reframes it as an identity/quota check ('Who am I and how much quota is left'). None of the siblings (get_docs, get_place, list_areas, search_places) overlap with this, so an agent can route to it unambiguously.

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?

Implies clear usage ('Who am I and how much quota is left') and explicitly covers the no-credential branch ('Works without a key too'). There are no true alternatives to name, but it stops short of stating any prerequisite or when-not-to-use condition.

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.