create_recharge
Create a recharge order for an account email
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | |||
| amount_cents | Yes |
Manto — 馒头新闻
TDQS
B3.3/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only reveals that the tool creates something, with no mention of side effects, prerequisites, currency handling, idempotency, or error behavior.
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?
A single sentence with no filler. The core action and target are stated immediately, making it easy to scan and act on.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description is thin. It leaves unanswered important context such as whether the email must reference an existing account, what a successful response looks like, and any monetary constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It adds meaning to email ('for an account email') but says nothing about amount_cents, its units, valid ranges, or how it relates to the recharge.
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 states a specific verb ('Create') and resource ('recharge order'), and clarifies that the order is tied to an account identified by email. This clearly distinguishes it from siblings like create_account and get_recharge.
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?
The wording implies this tool is used when a recharge order needs to be created for an account. However, it does not explicitly discuss when to prefer this tool over create_account or get_recharge, nor does it state any exclusions.
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.