Skip to main content
Glama

Nefesh — Real-Time Human State Awareness for AI

by ai.nefesh
OverviewDiscussionsAdmin

check_api_key_status

Check a pending API key authorization using its request_id.

Use request_id exactly as returned by request_api_key, never an email.
Poll every 10 seconds. awaiting_user means the user must open the URL;
pending means email verification is still required. ready returns the
API key once only. Store it and include it in all subsequent HTTP calls.
Stop on expired; ask the user before starting another authorization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / title
      Previous value: -"check_api_key_statusArguments"New value: +"CheckKeyStatusArguments"
  2. Added

TDQS

A5/5.0
Behavior5/5

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

No annotations, so description carries full burden. It describes states, polling cadence, one-time key return ('returns the API key once only'), what to do with it, and stop conditions. This is rich behavioral disclosure far beyond what the minimal schema provides.

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?

Short, front-loaded with the core action and critical parameter guidance, then sequential instructions. No wasted words; every sentence conveys necessary information.

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 no output schema, no annotations, and a single parameter, the description fully covers how to poll, interpret states, handle the returned key, and stop. Nothing essential is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and there is only one parameter, so description must explain request_id. It explicitly states 'Use request_id exactly as returned by request_api_key, never an email,' which is critical usage detail not in the schema (which merely says string).

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 ('Check') and resource ('pending API key authorization') and clearly distinguishes from the sibling request_api_key by indicating this is for an existing request_id, not generating a new one.

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?

Provides explicit polling interval (every 10 seconds), what to do in each state (awaiting_user, pending, ready, expired), and the stop condition with user consent needed before re-authorization. Leaves no ambiguity for the agent.

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

All Nefesh — Real-Time Human State Awareness for AI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources