Skip to main content
Glama

Prompt guide

prompt_guide
Read-onlyIdempotent

Get the house prompt grammar for a generation job, with the models to use for it and a worked example. Tasks: face_lock, character_outfit, character_sheet, scene_plate, video_scene, video_from_image, video_keyframes, story_bible. Call with no task for the index. Worth calling BEFORE run whenever you are making characters, scenes or video: a malformed request is rejected and a weak prompt wastes a paid generation, and this returns the exact params and the failure modes each grammar exists to prevent.

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

Input Schema

NameRequiredDescriptionDefault
taskNowhich job you are doing: face_lock, character_outfit, character_sheet, scene_plate, video_scene, video_from_image, video_keyframes, story_bible. Omit to list the tasks with a one-line summary of each.

Output Schema

NameRequiredDescriptionDefault
noteYes
tasksYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and non-destructive, and the description adds real value on top: it is a prerequisite lookup whose failure to consult leads to rejection or paid waste, and it returns failure modes per grammar. It does not describe output shape, but an output schema exists to carry that.

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

Conciseness4/5

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

Front-loads what the tool returns and the sequencing advice, so the important guidance is early. The task list appears twice (description and parameter schema), which is mild redundancy but not harmful.

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

Completeness5/5

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

For a single-parameter read-only guide tool with an output schema, the description covers purpose, invocation variants, timing relative to run, and the cost of skipping it. Nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100% and the single task parameter already enumerates the accepted values, including the omit-to-list behavior. The description restates the same task list rather than adding format, defaults or edge-case meaning, so it sits at the baseline for a fully documented schema.

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 ('Get the house prompt grammar for a generation job') plus what comes back (models to use, worked example). The task taxonomy and the 'call with no task for the index' clause make it clearly distinct from run and the other siblings.

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

Usage Guidelines5/5

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

Explicitly tells the agent to call this BEFORE run when making characters, scenes or video, and gives the reason: malformed requests are rejected and weak prompts waste a paid generation. That is a concrete when/when-not condition with the alternative named.

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