Skip to main content
Glama

API key status

api_status
Read-onlyIdempotent

Verify Elfa API access and plan limits by checking key tier, credit usage, remaining requests, and reachability; returns the earliest unix timestamp available for historical data.

Instructions

Check the Elfa API key tier, credit usage and remaining requests, and confirm the API is reachable. Free. historyFrom is the earliest time, in unix seconds, the events, market and calls tools read on this plan.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
keyYes
problemYes
reachableYes
historyFromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv4.8.0
    • addedOutput schema / properties / historyFrom
      Added value: +{
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "reachable",
      -  "key",
      -  "problem"
      -]New value: +[
      +  "reachable",
      +  "key",
      +  "historyFrom",
      +  "problem"
      +]
  2. First observedv2.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful context beyond annotations: the call is free, it reports credit usage and remaining requests, and it explains the plan-dependent historyFrom limit affecting other tools.

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?

The description is three short sentences, front-loads the core purpose, and includes only relevant plan-limit context. No sentence is wasted.

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?

Given zero parameters, rich annotations, and an output schema, the description is complete enough: it states what is checked, that the call is free, that it confirms reachability, and how historyFrom relates to the plan. Return-value details can safely be delegated to the output schema.

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?

The tool has zero parameters, so there are no parameter semantics to document. The description mentions historyFrom only as plan context for other tools, not as an input to this tool, which is appropriate for a zero-parameter status endpoint.

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 description uses a specific verb, "Check," and names concrete resources: API key tier, credit usage, remaining requests, and reachability. It is clearly distinguishable from sibling tools like events, market, and calls, which read data rather than report account/API status.

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 provides clear usage context: use this to inspect plan limits and confirm API reachability, and notes that the call is free. It does not explicitly state when not to use it or name an alternative, so it falls short of full when/when-not guidance.

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