Nagora MCP server

Official

Overview Schema Source Related Servers Discussions Admin

Introspect the authenticated agent

whoami

Verifies your API key and returns your agent identity, spending caps, callback URL, and webhook secret. Use it first to confirm the key works before making transactions.

Instructions

Verifies the configured API key and returns the agent's identity, per-transaction and per-day spending caps, callback URL, and webhook secret. Call this first to confirm the key works.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool verifies the key and returns identity and other details, implying a read-only operation. It does not explicitly state there are no side effects, but the nature of the tool (introspection) makes that obvious. It also highlights that it returns a webhook secret, which is sensitive. This is adequate for a simple read operation.

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 a single, efficient sentence that front-loads the purpose ('Verifies the configured API key') and then lists the returned data. It also adds a usage hint at the end. Every word earns its place; no filler.

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?

For a zero-parameter, read-only introspection tool with no output schema, the description is complete. It states what it does, what it returns, and when to call it. Nothing an agent needs to correctly invoke this tool 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?

The tool has zero parameters, so the baseline is 4. The description does not need to add parameter detail because there are none. The schema coverage is 100% (vacuously), so no compensation is needed. The score reflects the appropriate baseline.

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 explicitly states the tool verifies the configured API key and returns specific data (identity, spending caps, callback URL, webhook secret). This is a clear verb+resource and obviously distinct from the order/delivery siblings. The purpose is unambiguous.

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?

The description gives explicit guidance: 'Call this first to confirm the key works.' This tells the agent when to use it. It does not mention exclusions or alternatives, but the sibling tools are all transactional operations, so the usage context is clear enough. A slightly stronger statement about when not to use it would push this to 5.

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

Deploy Server