Skip to main content
Glama

Klinio

Get the account

get_account
Read-only

The plan and the credits left (for a free account, today's and when they renew).

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety needs no restating. The description does add genuinely new behavioral context: the returned values differ by account type, with free accounts exposing today's credits and a renewal date. It stops short of describing the shape or units of the credit figures, which matters because there is 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 short sentence with no padding, front-loading the two main returned values before the parenthetical qualifier. The parenthetical about free accounts is slightly compressed and reads awkwardly ('today's and when they renew'), costing a point on clarity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 is the only source of return-value information, and it covers only the highlights: plan, credits, and free-account renewal timing. It leaves unclear what a paid account surfaces (e.g., whether renewal or billing period appears) and gives no sense of units or format for the credit balance.

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 for the description to disambiguate; the baseline of 4 applies. The schema coverage figure is nominal given an empty properties object.

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 the specific resource contents (plan and remaining credits) plus the renewal-timing detail for free accounts, which is far more concrete than the title's bare 'Get the account'. It omits an explicit verb (the title supplies 'Get') and never contrasts itself with siblings, but its subject matter is distinct enough from the search-oriented siblings that confusion is unlikely.

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 mention of when the call is worthwhile versus other tools, and no prerequisites. The zero-parameter nature makes invocation trivially safe, but the description gives no cue about when an agent should fetch the account versus relying on other data.

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