Skip to main content
Glama

Publish the per-section plan

inspo_plan

Publish a section-by-section page plan from liked references, including primary/alternate picks, components, and design analysis, so users can review, edit, and approve before building.

Instructions

After analyzing the liked references (look at them with inspo_feedback, section by section), publish the plan of what goes in each section: the primary reference, alternates, components, and your analysis (layout, typography, color, imagery, motion, copy). It shows in the board's Plan tab, where the user can swap the primary for another like or any reference of that section, change the style or components, leave notes and approve. inspo_feedback returns the resulting plan (user edits win). Build from that plan.

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": {
      "summary": "<summary>",
      "sections": "<sections>"
    },
    "name": "inspo_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNoStyle item id (s-…) the page will use.
sessionNoSession id. Defaults to the most recent session in this project.
summaryYesThe overall direction in 2-3 sentences.
sectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it says the plan appears in the board's Plan tab, that the user can swap the primary, change style or components, leave notes and approve, and that user edits override the proposed plan. It does not cover permissions or whether an existing plan is overwritten, but the visible side effects and feedback loop are well disclosed.

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?

The description is front-loaded with when to use it and what it publishes, then explains the downstream user interaction. It is somewhat dense but each sentence supports the workflow or behavioral context, and there is no obvious filler.

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?

The tool has a nested section schema, no annotations, and no output schema, so the description needs to explain workflow and side effects. It does that well by covering the input analysis, Plan tab visibility, user approval/editing, and feedback loop. It could be more complete by describing what inspo_plan itself returns, but the essential context is present.

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 description coverage is 75%, so the schema already documents most parameters. The description adds useful meaning by naming the section-level contents (primary, alternates, components, and analysis dimensions) and the user-editable style/components. It does not add much beyond the schema for summary or session, so the baseline 3 is appropriate.

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 uses a specific verb and resource: publish the per-section plan. It enumerates the plan contents (primary reference, alternates, components, analysis) and distinguishes this tool from inspo_feedback by framing the latter as the input/feedback source.

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 gives a clear prerequisite and workflow: analyze liked references with inspo_feedback section by section, then publish the plan here. It also explains that inspo_feedback returns the resulting plan and that the user's edits win, which guides the follow-up loop. It does not explicitly state when not to use this tool, but the context is sufficiently clear.

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