Skip to main content
Glama

nephis_whoami

Inspect the current authenticated identity, tenant ID, active tier, resource limits (RAM, vCPU, projects), and security quarantine status to verify sandbox access and constraints.

Instructions

Inspect current authenticated identity, tenant ID, active tier, resource ceilings (RAM, vCPU, projects), and security quarantine status.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the burden, and "Inspect" plus the read-only nature of the enumerated fields implies a non-mutating call, but this is never stated explicitly. Nothing is said about whether the call is free, cached, or reflects live quota state — the quarantine/ceiling fields suggest live state but that is inferred rather than disclosed.

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?

A single sentence that front-loads the core purpose (identity inspection) and then packs the returned surface area into a compact parenthetical list. No filler, no restatement of the tool name.

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?

For a zero-parameter introspection tool with no output schema, enumerating the returned fields is exactly the right compensation, and it is largely done. The minor gap is that it doesn't say what the agent should do with the result — for example whether a quarantine status means calls will fail — but the core coverage is adequate.

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 takes zero parameters, so there is nothing in the input schema to interpret and no risk of parameter ambiguity. Baseline 4 applies for a parameterless tool.

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?

"Inspect current authenticated identity" gives a specific verb and resource, and the enumerated fields (tenant ID, tier, resource ceilings, quarantine status) make the scope concrete. It does not explicitly contrast itself with any sibling, but no sibling in the list covers identity/tenant introspection, so an agent can still discriminate it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description contains no when-to-use, when-not-to-use, or alternative guidance. It never says to call this first when bootstrapping a session, nor that it is unnecessary when identity is already known, leaving the agent to infer the trigger condition entirely.

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

Deploy Server

Other Tools