Skip to main content
Glama

generate_service_blueprint

Read-only

Generate a self-contained HTML service blueprint visualizing user actions, frontstage/backstage processes, evidence, and pain points. Supports single-actor Shostack or two-actor swim lanes with optional ideal-state comparison.

Instructions

Render a service blueprint as a self-contained HTML page. Supports two modes: (1) classic Shostack single-actor blueprint — user action, frontstage, backstage, support, evidence, pain/delight; (2) two-actor HI-loop blueprint — when actors is supplied, renders two swim lanes with a line of interaction between them (e.g. customer ↔ lawyer, patient ↔ doctor, buyer ↔ agent). Each actor gets their own actions, frontstage (what they see), and evidence. Optionally accepts an ideal-state to render side-by-side with the current state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idealNoOptional ideal-state blueprint — if provided, output shows current AND ideal side-by-side
actorsNoOmit for classic single-actor Shostack blueprint. Provide to render a two-swim-lane HI-loop blueprint with a line of interaction between the two sides.
currentYesThe current-state blueprint as an array of steps
subtitleNoShort description or context line under the title
service_nameYesName of the service (e.g. 'Free trial signup', 'Client intake', 'Restaurant reservation')
Behavior4/5

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

Annotations already provide readOnlyHint and non-destructive hints. The description adds valuable behavioral context: it generates an HTML page, supports two layout modes, and can render side-by-side states. This goes beyond annotations without contradicting them.

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 concise (3 sentences), front-loaded with the core purpose, and structured to present modes in a clear hierarchy. Every sentence adds value with no redundancy.

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?

Given the rich schema (100% coverage) and annotations, the description is nearly complete. It explains modes and optional states but could mention that the output is a self-contained HTML page (already stated) and that no persistent changes are made (implied by readOnlyHint). Minor gaps.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds extra meaning by explaining how 'actors' switch layout and how 'ideal' enables side-by-side rendering, providing semantic context beyond the 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?

The description clearly states it renders a service blueprint as a self-contained HTML page, distinguishes two modes (single-actor vs two-actor), and uses specific verbs and resource. This differentiates it from all sibling tools, none of which generate blueprints.

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?

The description explains when to use each mode (single-actor vs two-actor via 'actors' parameter) and the optional ideal-state, providing clear contextual guidance. It lacks explicit when-not-to-use statements, but the context is sufficient given no similar sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhinocap/raven-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server