Skip to main content
Glama
Sign In
Mirai MCP

Mirai MCP

by satuapps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Balance and quota

account_status
Read-onlyIdempotent

Retrieve your remaining guest quota without an API key, or paid balance and subscription windows when a key is set, for the Mirai API.

Instructions

Read remaining guest quota when MIRAI_API_KEY is unset, or paid balance and subscription windows when a key is set. Does not send a chat. Use list_models for prices.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds value by confirming it does not send a chat and explaining conditional behavior based on API key. No contradictions.

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?

Two sentences, front-loaded with the core action and conditions, followed by an explicit exclusion and sibling reference. No wasted words.

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 no output schema and no parameters, the description covers the main behaviors and usage conditions adequately. Could optionally mention what 'quota' vs 'balance' means, but not necessary for basic selection.

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 description doesn't need to elaborate. It still adds context about the conditional behavior (key vs. no key).

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 clearly states the tool reads account status (quota/balance) and distinguishes it from sending a chat. It also mentions a sibling tool for prices.

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

Usage Guidelines5/5

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

The description explains when to use this tool (depending on API key presence) and explicitly directs to list_models for prices, providing clear guidance versus alternatives.

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