Skip to main content
Glama

Get the Stick site guide

get_guide
Read-only

Start with the owner priorities, a short brief and the design workflow: the owner's requests and existing style come before the guide's defaults. Call with no arguments for the overview and menus. Then use topic archetypes with archetypeId for a default page structure, directions for starting style kits, blocks with blockTypes for layout/Style advice and the exact schema, or examples with exampleId for a worked design. Images and sections are optional; intentional native photo placeholders are supported. Call before creating or changing a site.

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

Input Schema

NameRequiredDescriptionDefault
topicNoDefault overview: owner priorities, design workflow and menus. blocks: layout/Style advice and exact schema. archetypes: default page structures. directions: starting style kits. examples: section recipes and worked designs. all: complete guide.
exampleIdNoFor topic examples: choose an id from the overview, or omit for all examples.
blockTypesNoFor topic blocks: request only the block types you plan to use; omit for all existing blocks.
archetypeIdNoFor topic archetypes: choose an id from archetypeMenu, or omit for all archetypes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: it is a read-only advisory source, it supports intentional native photo placeholders, and images/sections are optional. It does not describe response size or pagination, which keeps it below a 5.

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 content is front-loaded with the workflow and then the per-topic routing, and every sentence carries actionable information. The prose is dense and somewhat run-on ('blocks with blockTypes for layout/Style advice and the exact schema'), which costs a point on readability but not on substance.

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 read-only guide tool with zero required parameters, full schema coverage and no output schema, the description covers purpose, sequencing and per-topic routing adequately. It could say more about what the returned guide content looks like, but nothing essential to correct invocation is missing.

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 coverage is 100% and enums are documented, so the baseline is 3. The description goes beyond that by explaining the pairing between topic values and their companion parameters (archetypes→archetypeId, blocks→blockTypes, examples→exampleId), which the schema alone does not make explicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description makes clear this is a documentation/guide retrieval tool ('Start with the owner priorities, a short brief and the design workflow'), with a specific resource (the Stick site guide). It is distinguishable from the CRUD siblings (get_site, create_site, update_site) by its advisory nature, though it never names a sibling explicitly.

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?

It gives explicit routing: no arguments for overview/menus, topic=archetypes with archetypeId, topic=directions, topic=blocks with blockTypes, topic=examples with exampleId. It also states a clear precondition: 'Call before creating or changing a site.' That is when-to-use guidance an agent can act on directly.

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