create_account
Create a passwordless Manto account
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| Yes |
Manto — 馒头新闻
TDQS
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It discloses that the operation is a creation and mentions 'passwordless', which hints at the auth mechanism, but it does not describe side effects, email verification, idempotency, duplicate-email behavior, or any required permissions. Basic mutation semantics are present, but significant behavioral context is missing.
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 sentence that is front-loaded and contains no filler. Every word adds meaning, making it appropriately sized and structurally effective.
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?
Given the simple schema and sibling context, the description is too thin. It lacks any information about what 'passwordless' means in practice, what happens after account creation, error cases, or return values. An agent would likely need to inspect external docs or experiment to invoke it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/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 for the email parameter. It does not mention email at all, nor explain how or why it is used. The agent is left to infer that email identifies the account from the parameter name alone.
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 'Create a passwordless Manto account' uses a specific verb (create) and resource (passwordless Manto account), clearly distinguishing it from sibling tools like get_account or create_recharge. It states exactly what the tool does without ambiguity.
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 description implies its usage: when you need to create a passwordless Manto account, call this tool. However, it provides no explicit guidance about when to prefer this over alternatives or any exclusions. The intended context is clear but not elaborated.
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.