Skip to main content
Glama

Plan a fruit story

fruit_story_guide
Read-onlyIdempotent

AI Fruit Story: a short, dramatic and funny soap opera of 3D cartoon fruit people (a human body, the head is a fruit) for TikTok, with talking scenes, captions and music. This returns the ready-made fruit people, roles, personalities, plots, options and prices, and (with a cast) the exact prompts MakeViral's own writer gets. With a draft it also checks your story and gives its exact price, without any charge. You can write the story yourself and send it to start_fruit_story as draft, or send only the cast and idea and MakeViral writes it.

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": "fruit_story_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
castNo1-3 fruit people
ideaNoOne line, or a few 'Name: line' lines the story must use
draftNoYour own story: the JSON the writer prompt of fruit_story_guide asks for (title, looks, numbers, scenes).
plotsNoUp to 2 plot ids (fruit_story_guide)
styleNo
captionsNo
languageNo
sceneCountNoScenes of about 8 s each. Default 6.

Output Schema

NameRequiredDescriptionDefault
checkNo
guideYes
choicesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotent, non-destructive), so the bar is lower, and the description adds genuine behavioral detail beyond them: that a `draft` triggers validation plus an exact price quote at no charge, and that the response includes ready-made cast assets, plots, options and pricing. It does not discuss rate limits, size limits or how pricing is computed, but the output schema carries return-shape detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences that front-load the concept, but the opening clause spends many words on genre flavour and a parenthetical ("a human body, the head is a fruit") before the agent learns what the call returns. The second sentence is a run-on packing three separate behaviors (returns, free draft check, handoff to start_fruit_story).

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only planning tool with rich annotations and an output schema, the description covers what an agent needs: what comes back, that a draft is validated free of charge, and how the result feeds start_fruit_story. The remaining gap is the untouched enum and numeric parameters, which the schema documents well enough to call correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description explains the two parameters with non-obvious effects: `cast` unlocks the exact writer prompts, and `draft` triggers a free check plus price. With schema coverage at 63%, however, `plots`, `style`, `captions`, `language` and `sceneCount` get no treatment in the description, so the meaning added is partial rather than compensatory.

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 a specific resource (fruit story planning: fruit people, roles, personalities, plots, options and prices) and even previews the exact writer prompts it will return, which distinguishes it from start_fruit_story, the tool that actually produces the story. It is slightly muddled because the first sentence describes the creative product (a TikTok soap opera) rather than the tool's operation, so the agent must read the second sentence to learn what a call returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the alternative path explicitly: write the story yourself and send it to start_fruit_story as `draft`, or send only cast and idea and let MakeViral write it. It also signals the cost condition ("without any charge" with a `draft`), which is real selection guidance. It stops short of saying when NOT to call this (e.g. versus the other guide variants), so no exclusions are stated.

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