Skip to main content
Glama

Feature Library

Get a page shape

get_shape
Read-only

Free. The page shapes: starting points for a whole page by kind (app workspace, dashboard, product reveal, service landing, story, personal homepage, event, shop, game), each with its reader’s job, reading path, first screen, header, structure, phone, motion, what fits and what not to do. Without an id, the list; with an id, the shape in full; with "compose", the method for a page no shape fits, with a worked example. A shape is where to start, never a template: pick one or compose, and name it in your notes.

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_shape"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOptional: a shape id, or "compose".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds context annotations cannot: the call is free (no credit cost), the return shifts shape depending on the argument (catalog vs single shape vs method with worked example), and it enumerates the content facets each shape carries (reader's job, reading path, first screen, structure, phone, motion, fits/anti-patterns). The remaining gap is return format — prose versus structured fields is unstated and there is no output schema to fall back on.

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

Conciseness3/5

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

Everything stated is informative, but it is delivered as one sprawling sentence with a long parenthetical enumerating eight kinds and nine content facets, which makes it slow to scan. Leading with "Free." as a standalone fragment delays the actual purpose, and the mode-mapping clause, the most actionable part, sits in the middle rather than up front.

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 one-parameter, read-only lookup with no output schema, the description does most of the work: it explains the argument's effect, what content comes back, and how to use the result. The main unresolved question is the response shape (free-form text versus structured sections), which matters because there is no output schema to consult.

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 the single parameter is already documented as a shape id or "compose", so the baseline would be 3. The description goes further by mapping each argument state to a distinct behavior — omitted yields the list, a concrete id yields the full shape, the literal "compose" yields the fallback method — which is meaning the schema does not convey.

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 names the resource concretely — page shapes, described as starting points for a whole page by kind, with an explicit enumeration of the eight kinds covered. It also spells out the three retrieval modes (list, full shape by id, compose method). It stops short of differentiating itself from siblings like get_playbook or get_brief, so an agent must infer that 'shape' is a distinct artifact type.

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

Usage Guidelines3/5

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

There is real guidance on mode selection — no id returns the list, an id returns the shape in full, "compose" returns a method — and a normative instruction to pick one or compose and name it in notes. What is missing is when to reach for this tool versus its resource-getter siblings, and whether a shape is a prerequisite for any later call.

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