Skip to main content
Glama
TimWongUp

keepygaga

by TimWongUp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

create

Create new dynamic Markdown pages after full-batch validation. Uses facts and aliases to build durable personal memories and returns page snapshots for reuse.

Instructions

Create new dynamic pages after full-batch validation. On applied, reuse returned Page Snapshots and receipts; do not call read or list solely to verify success.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesPage creations validated as one batch; repeated paths are rejected.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.7.0
    • changedInput schema / $defs / CreateOperation / properties / aliases / maxItems
      Previous value: -8New value: +6
    • addedInput schema / $defs / CreateOperation / properties / description / maxLength
      Added value: +80
    • changedInput schema / $defs / CreateOperation / properties / facts / maxItems
      Previous value: -50New value: +30
    • changedInput schema / $defs / Fact / properties / basis / description
      Previous value: -"Evidence basis: stated for the user's explicit statement; observed only where the Agent Contract permits a repeated behavioral observation."New value: +"Evidence basis: stated for the user's explicit statement; observed for Agent derivation or inference from current visible material."
    • changedInput schema / $defs / Fact / properties / content / maxLength
      Previous value: -4096New value: +800
    • changedInput schema / properties / operations / maxItems
      Previous value: -20New value: +15
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations are mostly negative flags and provide little behavioral context. The description adds meaningful behavior: full-batch validation, applied-mode side effects, and a prohibition on verification reads. It does not describe failure or partial-failure behavior, but the added context is valuable.

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?

Two sentences with no filler. The first scopes the action, and the second provides the most important post-call behavior and an explicit exclusion of read/list verification.

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 a rich input schema and an output schema available, the description covers the key operational context: batch validation, snapshot/receipt reuse, and not re-reading to verify. Minor gaps are the undefined 'dynamic pages' term and lack of failure behavior, but they do not block correct invocation.

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?

The only parameter, operations, is fully documented in the schema including CreateOperation fields, constraints, and repeated-path rejection. The description adds no parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource: 'Create new dynamic pages after full-batch validation.' The batch behavior is clear, but 'dynamic pages' is not defined and the sibling 'add' is not explicitly differentiated, so it does not earn 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?

Provides explicit post-call guidance: reuse returned Page Snapshots and receipts, and do not call read or list solely to verify success. This is strong when-not/alternative guidance, though it does not clarify when create should be chosen over the sibling add.

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