Skip to main content
Glama
mcp-server-everesteer

mcp-server-everesteer

Connection & key scope check

whoami
Read-onlyIdempotent

Verify API key authentication, SHA-256 fingerprint, scope, open gates, and available toolsets to confirm which Everesteer capabilities and permissions your session currently holds.

Instructions

Confirm API key authentication, SHA-256 fingerprint, scope, open gates, and toolsets.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
gatesNo
notesNo
scopeNounauthenticated
base_urlYes
identityYes
toolsetsNo
authenticatedYes
status_detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the safety profile. The description adds that it confirms specific items like SHA-256 fingerprint and open gates, which gives useful context about what information is surfaced, but it does not describe error behavior or authentication prerequisites beyond the implied API key.

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, front-loaded sentence that lists the key items checked. Every word contributes to conveying what the tool verifies, with no unnecessary filler.

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?

Given the tool's simplicity (no parameters, rich annotations, and an output schema), the description covers sufficient ground by listing the specific items confirmed. It could be slightly improved by noting behavior on failed authentication, but for a diagnostic tool this is largely complete.

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 appropriately adds no parameter details since none exist.

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 states a specific verb 'Confirm' and a concrete list of resources: API key authentication, SHA-256 fingerprint, scope, open gates, and toolsets. This clearly identifies an identity/auth diagnostic tool, though it does not explicitly differentiate itself from siblings like get_capabilities or get_health.

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?

There is no guidance on when to use this tool versus alternatives such as get_capabilities or get_health. The description merely states what it does, leaving the agent to infer that it is for checking authentication status.

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