Skip to main content
Glama

Kobo Terminal NGX

Key info and usage

get_my_usage
Read-onlyIdempotent

Your plan, requests used today, daily limit, per-minute limit and lifetime requests. Plan: Free+.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description's added value is enumerating the returned metrics, but it says nothing about who the 'my' refers to (API key vs. user), whether counters reset on a schedule, or what happens when the limit is exceeded.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The metric list is front-loaded and wastes no words, which is good. However, the trailing fragment 'Plan: Free+.' is ambiguous — it reads like a hardcoded/stale plan label rather than a statement about the tool, and could mislead an agent into thinking the caller's plan is always Free+.

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 trivial zero-argument read tool with no output schema, the description covers the important part: what data comes back. It is nearly complete; only the identity/scope of 'my' and reset or error behavior are left unstated, which are minor for this complexity level.

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?

There are zero parameters, so the baseline is 4; there is no parameter semantics to get wrong. The description does not falsely suggest any inputs.

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 names concrete fields returned (plan, requests used today, daily limit, per-minute limit, lifetime requests), which makes the tool's purpose as an account/quota introspection call unambiguous. It doesn't explicitly contrast itself with any sibling, but the siblings are all market-data lookups, so the distinction is implicit rather than stated.

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 implied — call it to check your plan and request budget — but there is no explicit statement of when to use it (e.g. before hitting rate limits) and no named alternatives or exclusions. For a zero-parameter account tool this is acceptable but leaves the agent to infer the trigger condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources