Skip to main content
Glama

storyline.suggest

Suggest next scenes for the project's storyline from its premise (metered in credits unless the owner uses their own Anthropic key). Requires storyline.set_premise first. The suggestions become candidates; choose one with storyline.pick.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "storyline.suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
guidanceNo
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose two non-obvious traits: the operation is metered in credits unless the owner supplies their own Anthropic key, and the output is non-destructive candidate state rather than an applied change. It does not cover failure modes, latency, or cost magnitude, which leaves a modest gap for an LLM-backed generation call.

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?

Three short sentences, front-loaded with what the tool does, then cost/precondition, then the follow-up action. No filler, no restatement of the title, and each sentence adds information an agent needs.

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?

With no annotations and no output schema, the description covers the cost model, prerequisite, and the candidate/pick handoff well, but it never indicates what a suggestion actually looks like or how the two tuning parameters shape results. For a creative-generation tool with three undocumented parameters, that is adequate-but-incomplete.

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% and the description mentions none of the three parameters — 'count' (2-6) and 'guidance' (1-1000 chars) are completely unexplained in both places. Only projectId's meaning is inferable from 'the project's storyline', so the description fails to compensate for the schema gap.

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?

States a specific verb and resource — 'Suggest next scenes for the project's storyline' — plus the input it derives from ('from its premise'). It is cleanly separable from storyline.set_premise (precondition) and storyline.pick (follow-up), so an agent can place it in the workflow without opening a schema.

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?

Gives an explicit prerequisite ('Requires storyline.set_premise first') and an explicit next step ('choose one with storyline.pick'), which is exactly the routing an agent needs in a multi-step storyline flow. It lacks any when-not/exclusion guidance (e.g., what to do if candidates already exist), keeping it just short of a 5.

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.