Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

whoami

What this API key can do: kind (user / partner / agent), scopes, rate limit, monthly quota, cli_release (latest / minimum_supported — is this build behind), endpoints (entry-point policy), and operations.available / operations.unavailable (with missing_scopes_any or not_allowed_for_kind). Call this before concluding a capability does not exist — a missing tool or a 403 is usually an ungranted scope. Advisory (server is the authority). Free, cached 5 minutes.

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

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden and does reasonably well: it flags itself as advisory with the server as authority, free, and cached for 5 minutes. It does not say whether the call itself requires any scope, what an error looks like, or whether the cache can be bypassed. The `cli_release` note adds useful interpretive context about build staleness.

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?

It is front-loaded with the returned capability surface, then the single most important instruction in bold, then caveats about authority and caching. The parenthetical field annotations are dense but each carries information. No filler sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must stand in for one, and it does by enumerating the response fields and the `missing_scopes_any` / `not_allowed_for_kind` reason codes. Combined with the advisory and cache notes, an agent has enough to call and interpret it. Minor gap: no differentiation from the similarly named `capabilities` sibling.

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

Parameters3/5

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

All six parameters are infrastructure wrappers (`_jq`, `_spill`, `_fields`, `_intent`, `_max_bytes`, `_max_bytes_mode`) and schema coverage is 100%, so the baseline of 3 applies. The description says nothing about these parameters, but the schema already documents them fully.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the resource returned: what the current API key can do, enumerating `kind`, `scopes`, rate limit, monthly quota, `cli_release`, `endpoints`, and `operations.available`/`unavailable`. That is far more specific than the bare name `whoami`. It does not, however, distinguish itself from the sibling `capabilities`, which an agent could plausibly confuse it with.

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 gives an explicit trigger: call this before concluding a capability does not exist, with the rationale that a missing tool or a 403 usually means an ungranted scope. That is strong conditional guidance. It stops short of stating when not to call it or naming a sibling alternative to use instead.

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