Skip to main content
Glama

journal-page-create

Add a page to an existing journal entry. Text pages take HTML content: style with inline style="" attributes (Foundry strips and ), link documents with @UUID[Actor.]{Label}. handout-template-list offers ready-made layouts.

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": {
      "journalId": "<journalId>",
      "name": "<name>"
    },
    "name": "journal-page-create"
  }
}

Input Schema

NameRequiredDescriptionDefault
srcNoSource file path or URL for image/video/pdf pages
nameYesName of the new page
typeNoType of page (default: text)
contentNoHTML content for text pages
journalIdYesThe journal ID to add the page to
categoryIdNoPage category of this journal (bridge module 8.19.0+, Foundry 13+)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / categoryId
      Added value: +{
      +  "description": "Page category of this journal (bridge module 8.19.0+, Foundry 13+)",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent), so the description's main contribution is the sanitization rule: Foundry strips <style> and <script>, so styling must be inline. That is exactly the kind of non-obvious behavioral constraint an agent would otherwise learn only from a failed call.

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, front-loaded with the core action and followed by the most failure-prone detail (HTML/sanitization) and then the alternative resource. No sentence is filler.

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?

With full schema coverage, annotations, and no output schema, the description covers the essentials: what the tool does and how content must be authored. Minor gaps remain around image/video/pdf handling and what the response returns, but nothing critical to invoking it correctly is missing.

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%, so every parameter including type, content, src, and categoryId is already documented, which sets the baseline at 3. The description adds real meaning for content by specifying HTML with inline styles and @UUID link syntax, but says nothing extra about src or categoryId beyond the schema.

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 page to an existing journal entry" gives a specific verb (add) and resource (page within a journal entry), which distinguishes it cleanly from journal-page-update, journal-page-delete, and journal-page-get. It stops short of naming any sibling as the wrong tool for a given case, so it lands just under a 5.

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 supplies concrete usage context: text pages take HTML, styling must be inline, and handout-template-list offers ready-made layouts. That routes the agent to a useful sibling for a common need, though it gives no explicit when-not-to-use (for example, that existing pages should be changed with journal-page-update).

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