Skip to main content
Glama

Add a page to a Space

spaces_add_note

Add a published page to the end of a Space. Needs the owner or editor role. Adding a page that is there already changes nothing.

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": {
      "spaceId": "<spaceId>",
      "slug": "<slug>"
    },
    "name": "spaces_add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesA page slug from search_collection or get_note, for example "concepts/teaming/team-topologies".
spaceIdYesThe Space id, from spaces_list_spaces.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare non-read-only, non-destructive, closed-world; the description adds genuinely new facts: the append-at-end ordering, the required owner/editor role, and idempotency ("adding a page that is there already changes nothing"). It does not describe the response payload, but with no output schema that gap is modest rather than fatal.

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 short sentences with the core action first, then permissions, then the idempotency edge case. Nothing is repeated from the schema or annotations and nothing could be cut without losing information.

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 mutation with full schema coverage and safety annotations, the description covers action, authorization, ordering and repeat-call behavior. Only the return shape is unaddressed, which is minor given there is no output schema.

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 100%, and both parameters document their own provenance (slug from search_collection or get_note, spaceId from spaces_list_spaces). The description adds only the indirect hint that the page must be published, so baseline 3 is right.

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?

"Add a published page to the end of a Space" gives a specific verb, resource and insertion position, which is enough to distinguish it from spaces_remove_note without opening the schema. It stops short of naming any sibling explicitly, so sibling differentiation is implied rather than stated.

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?

It states the prerequisite (owner or editor role) and the no-op case, which helps an agent decide whether it can call at all. However it never says when to prefer this over adjacent tools such as spaces_share_document or tools_create_document, leaving the main selection decision to inference.

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