Skip to main content
Glama
Sign In
overwing-mcp

overwing-mcp

by frod27
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Who am I

whoami

Determine the organization, plan, and billing setup linked to the current API key.

Instructions

Identify the organization and plan behind the configured API key, and whether billing is set up.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden of disclosing behavior. The verb 'identify' clearly communicates a read-only, non-mutating operation, and the description goes beyond the tool name by stating exactly which details are reported: organization, plan, and billing setup. This is sufficient for a simple introspection call.

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, well-formed sentence with no filler or redundancy. The key information is front-loaded and every word contributes to the tool's purpose and behavior.

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 the tool has no parameters)Skip and no output schema, the description is complete: it tells the agent what the tool does and what information it returns. Nothing essential is missing for an agent to decide whether and how to call it.

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 input schema has zero parameters, so there is nothing to explain. The description adds useful meaning by enumerating the response aspects (organization, plan, billing setup), which is the relevant semantic content for this tool.

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 uses a specific verb ('Identify') and clearly names the resources it covers: the organization and plan behind the configured API key, plus billing setup status. This clearly distinguishes it from sibling tools like list_plans or get_usage, which address different resources.

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 makes the usage context clear by tying the tool to the 'configured API key' and its associated organization, plan, and billing status, which tells an agent when to call it. It does not explicitly name alternatives or exclusions, but the intent is clear enough for a no-parameter introspection tool.

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