Skip to main content
Glama

K-EXAONE status & usage

exaone_status
Read-only

Check k-exaone-mcp settings, accumulated token usage, and EXAONE API rate-limit headers; optionally send a tiny request to verify API key and connectivity.

Instructions

Show k-exaone-mcp settings, token usage accumulated by this server process, and the latest EXAONE API rate-limit headers. With ping=true (default) it also sends one tiny request to verify the API key and connectivity.

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

Input Schema

NameRequiredDescriptionDefault
pingNoSend a tiny test request (uses a few hundred tokens). Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, which could mislead an agent into assuming a pure local read; the description corrects this by disclosing that ping=true fires a real network request that costs a few hundred tokens. It also scopes token usage to 'this server process.' It does not say what happens if the ping fails (error vs. reported status), which keeps it below 5.

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, no filler. The three returned data categories are front-loaded and the conditional ping behavior follows immediately after, matching the order an agent needs to reason about the call.

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, the description usefully enumerates what the response contains and warns about the token cost of the default path. The main gap is failure behavior when the ping request fails, and there is no mention of auth requirements for the API key being verified.

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?

Schema coverage is 100% so the schema already documents the single boolean, but the description adds real meaning: what the flag actually does (verify API key and connectivity), its cost (a few hundred tokens), and that true is the default. That is more than the schema conveys.

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?

Uses a specific verb ('Show') plus an enumerated resource set: settings, per-process token usage, and rate-limit headers. An agent can tell this is a diagnostics/status tool rather than a model-query tool, though it never names the sibling ask_exaone to sharpen the contrast.

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

Usage Guidelines3/5

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

Usage is only implied — the enumeration of settings/token usage/rate limits signals 'check health or quota.' There is no explicit statement of when to prefer this over ask_exaone, nor any when-not condition or prerequisite.

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