Skip to main content
Glama
the-real-talk

the-real-talk

create_page

Creates a new page and returns its ID for parent references; rejects duplicate names and changes the active page only when requested.

Instructions

Create a new page in the document (refuses an existing name). Returns its ID, usable as parentId in build_tree, create_component_instance, set_parent. The active page is changed only if activate is true.

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": {
      "name": "<name>"
    },
    "name": "create_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
activateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It usefully discloses the duplicate-name refusal (an error behavior) and the conditional side effect on the active page, but says nothing about permissions, whether the new page starts empty, or where it is positioned in the document.

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?

Three tight sentences with no filler, and the core operation plus its failure mode are front-loaded ahead of return value and side-effect details.

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 creator with no output schema, the description covers creation semantics, duplicate handling, return value, and the activate side effect. Only permission requirements and initial page content are left unstated, which is a minor gap.

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 0%, so the description must supply meaning. It does: 'refuses an existing name' defines the uniqueness constraint on name, and the final sentence explains that activate controls whether the active page is switched, which is more than the boolean type conveys.

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?

States a specific verb and resource ('Create a new page in the document') and implicitly separates itself from rename_page/delete_page/set_current_page by focusing on creation. The parenthetical about refusing duplicate names pins down the exact semantics of the operation.

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 tells the agent where the returned ID is consumed (build_tree, create_component_instance, set_parent) and the condition under which the active page changes. It stops short of naming a sibling to use instead in any scenario, so no explicit when-not guidance.

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

Deploy Server

Other Tools