get_account
Get account quota, balance and recent content
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Manto — 馒头新闻
TDQS
B3.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It only says 'Get', which implies read-only behavior, but it does not explicitly state side effects, permissions, data freshness, pagination, or any other behavioral trait. The description does not go beyond what the name already suggests.
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 description is a single concise, front-loaded sentence that names the resource and the three data categories. Every word contributes directly to understanding, with no filler or repetition.
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?
The tool is simple with no parameters and no output schema, and the description does name the return categories. However, it does not clarify how 'recent content' relates to sibling tools like list_account_articles, nor does it describe the response format, leaving some ambiguity for tool 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 and the schema coverage is 100%, so there is no parameter ambiguity. With no parameters to document, the description is not required to explain parameter meaning, and the baseline of 4 applies.
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 states a clear verb ('Get') and resource ('account'), and specifies the data returned: quota, balance, and recent content. It does not explicitly differentiate from siblings like lookup_account or list_account_articles, but the scope is still concrete enough to understand the tool's primary function.
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 guidance on when to use this tool versus alternatives such as lookup_account or list_account_articles. The description does not state exclusions, fallbacks, or any selection criteria, leaving the agent to infer usage from the name and description alone.
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.
TDQS
B3.1/5.0
Disambiguation4/5
Most tools target distinct resources and actions, such as account creation versus lookup versus article listing. Minor overlap exists between get_account (which includes recent content) and list_account_articles, but the descriptions are clear enough to avoid serious misselection.
Naming Consistency4/5
The naming mostly follows a clear verb_noun pattern, e.g., create_account, get_recharge, remove_content, set_promotion. A few tools like publish and search are bare verbs, creating a minor inconsistency, but the overall pattern remains predictable and readable.
Tool Count5/5
Ten tools is well-scoped for a news content management platform covering accounts, publishing, searching, recharges, and promotion. Each tool serves a distinct functional need without unnecessary bloat.
Completeness4/5
The server covers core content lifecycle operations with publish (create/update), remove_content (delete), list_account_articles (read), and search. Minor gaps exist such as no explicit get/delete for accounts or a way to view current promotion settings, but the main workflows are supported.