Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Who am I

whoami
Read-onlyIdempotent

Retrieve the current Mergestorm account, API key prefix, plan, API base, and server version to verify credentials and environment.

Instructions

The Mergestorm account this key belongs to (GitHub login or email), the key prefix, plan, API base, and the version of this running mergestorm-mcp server.

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.2.31

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered. The description adds real value beyond that by disclosing the returned payload fields (key prefix, plan, API base, server version), which is the key behavioural content for a zero-argument read tool with no output schema.

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?

A single sentence with no padding, front-loaded with the primary datum (the account) followed by supplementary metadata. It is slightly list-like and lacks a leading verb, but nothing is wasted.

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?

With no output schema and no parameters, the description's job is to describe the return values, which it does field by field. It could be marginally stronger by noting that results reflect the key's own credentials rather than a target account, but an agent has enough to call it correctly.

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 to disambiguate; the baseline of 4 applies. The description correctly adds no source or filter parameters, implicitly confirming the call is context-derived from the API key.

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 enumerates exactly what the tool reports: account identity (GitHub login or email), key prefix, plan, API base, and server version. That makes the resource unambiguous and clearly distinct from the settings/repo/stack siblings, even though it never uses an explicit verb like 'return' or 'identify'.

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 when-to-use guidance, no prerequisites (e.g. 'requires a valid API key' is only implicitly signalled by 'this key belongs to'), and no mention of alternatives. An agent must infer that this is a diagnostics/identity check rather than a filtered lookup.

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