Login to an existing FableMaker account. Returns a JWT token that expires in 26 days. Use this token as Bearer auth for subsequent MCP calls.
| Name | Required | Description | Default |
|---|---|---|---|
| password | Yes | Your password | |
| username | Yes | Your username |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses token expiration (26 days) and usage, but lacks information on error conditions or rate limits. With no annotations, more detail could be helpful.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences front-loading purpose and action, no unnecessary text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple authentication tool with two parameters and no nested objects or output schema. Could mention prerequisite for other tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema descriptions already cover username and password; description adds no further meaning beyond 'your username/password'. Schema coverage is 100%, so baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states it logs into an existing account and returns a JWT token, differentiating from signup sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly instructs to use the returned token as Bearer auth for subsequent calls, but does not explicitly mention when not to use (e.g., already logged in).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools have mostly distinct purposes. The only potential overlap is between create_story and quake_story, but quake_story is explicitly a 'do-over' with limitations, so confusion is minimal.
Most tools follow verb_noun pattern (e.g., create_story, get_balance), but 'login' and 'signup' are single verbs, and 'quake_story' uses an unconventional verb. This is a minor inconsistency.
With 10 tools covering account management, payments, story CRUD, and specialized operations (quake, remix), the count is well-scoped for the platform's purpose.
Covers core lifecycle (create, read, list, delete stories) plus payments and authentication. Missing update_story for editing metadata, but this is a minor gap.