Skip to main content
Glama

Page sections: recommend or set

inspo_sections

Lists every website section and app screen available for research, plus recommended section sets per project type. Set or update the session's page order plan once agreed with the user.

Instructions

Without sections: returns every website section and app screen inspo can research, plus recommended sets per project type (websites: landing, ecommerce, restaurant, studio, saas, portfolio, services; web systems: webapp, admin; apps: mobile, mobile-commerce, booking), to help you recommend them to the user. Mix freely (e.g. a SaaS marketing site + its dashboard). With sections: sets the session's section plan (page order), replacing the previous one.

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

Input Schema

NameRequiredDescriptionDefault
sessionNoSession id. Defaults to the most recent session in this project.
sectionsNoPage sections to research, in page order. Agree on them with the user first (see inspo_sections).

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, the description carries the full burden and does meaningful work: it identifies the no-argument call as a read of the available catalog and the argument call as a mutation that 'replacing the previous one' — an explicit disclosure that an existing plan is overwritten. It does not cover permissions, session scoping, or what the write returns, but the destructive replace semantics are surfaced explicitly.

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 'Without … / With …' split is well front-loaded and immediately scannable. The long parenthetical of project types (landing, ecommerce, restaurant, studio, saas, portfolio, services, webapp, admin, mobile, mobile-commerce, booking) is somewhat bulky, though it does convey which preset sets exist.

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 two-parameter tool with no output schema and no annotations, the description covers both modes, the catalog content, the recommendation presets, mixing guidance, and the replace-on-write behavior. Only the shape of the returned catalog and preset data is left implicit, which is a minor gap for a read-then-write tool.

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%, so both `session` and `sections` are already documented in the schema, including the session default and the `id` enum. The description adds some meaning — `sections` is a page-ordered plan that supersedes the prior one — but says nothing about `session` or about how `why`/`notes` should be used, so it is a modest increment over 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 states two concrete behaviors keyed on the presence of one parameter: a read that returns the full section catalog plus recommended sets per project type, and a write that sets the session's page order. The enumerated project-type groupings make the returned resource concrete rather than abstract.

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 'Without `sections` … With `sections` …' framing tells the agent exactly which mode applies and when, and 'to help you recommend them to the user. Mix freely' gives the intended workflow. It stops short of naming a sibling tool for alternative planning paths or any exclusion, so it is clear context rather than full routing guidance.

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