Skip to main content
Glama
mergestorm-mcp

mergestorm-mcp

Official

Credits

credits
Read-onlyIdempotent

Retrieve current standard-credit usage and reset time to monitor available allowance and plan when limits renew.

Instructions

Current standard-credit usage and reset time.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.31

TDQS

A3.5/5.0
Behavior3/5

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

The description confirms the non-mutating, reporting nature of the tool by referencing 'usage and reset time'. This aligns with the `readOnlyHint: true` annotation but adds context about the nature of the returned data rather than just its safety profile.

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 definition is perfectly sized and highly direct. It communicates the tool's entire function in one single, efficient sentence without any unnecessary phrasing.

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 status check tool, the definition is complete enough. It identifies exactly what the agent needs to know (credits and timing) to safely invoke the function.

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?

Since the tool accepts zero parameters and the schema coverage is 100%, the description maximizes its semantic value by defining the resource scope explicitly. No additional parameter context was needed.

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 clearly defines the resource being accessed (standard credits) and the specific data retrieved (usage and reset time). This is a specific declaration of function, distinguishing it from potential broader financial tools.

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 definition provides no guidance on the optimal time to use this tool or if it conflicts with other potential credit-related APIs. Usage is left entirely to inference based on the tool's function.

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