Skip to main content
Glama
TimWongUp

keepygaga

by TimWongUp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add

Destructive

Add facts to a page, optionally updating its description, using a version snapshot to ensure consistency.

Instructions

Add independent Facts and optionally replace the page description using its latest Page Snapshot. Group Facts for one page in one operation. On applied, reuse returned Page Snapshots and receipts; do not verify with read or list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYesFact additions validated as one batch; each path must be unique.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.2
    • addedInput schema / $defs / AddOperation / properties / description
      Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 80,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Replacement page description to apply with the Fact addition.",
+  "title": "Description"
+}
  2. Changed4 schema fields changedv0.7.0
    • changedInput schema / $defs / AddOperation / 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
  3. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description confirms this by saying the page description may be 'replace[d]'. It adds meaningful context beyond annotations: the operation is snapshot-versioned ('using its latest Page Snapshot'), batch-validated, and returns snapshots/receipts that should be reused rather than verified via read/list — a workflow contract the annotations cannot express.

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 sentences, each earning its place: core purpose, batching rule, and post-apply workflow. The main function is front-loaded in sentence one, and there is zero filler or repetition of schema content.

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 moderately complex batch-write tool, the combination is complete: a rich 100%-coverage schema documents every parameter, annotations cover the safety profile, an output schema exists, and the description supplies the missing operational nuance (snapshot provenance, no-verify rule, grouping). The only small gap is that the description never explains where the initial Page Snapshot comes from, though the schema's if_version description partially covers this.

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 the schema fully documents operations, path, if_version, facts, basis, content, and description. The description adds only marginal value by linking 'latest Page Snapshot' to the if_version parameter and reinforcing the batching semantics of operations. At 100% coverage the baseline of 3 is appropriate.

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 states a specific verb+resource: 'Add independent Facts' to a page, with a secondary behavior of optionally replacing the page description. This clearly separates it from read/list in intent. However, it does not explicitly distinguish itself from the closely related mutation siblings create and update — the differentiation is implied by the word 'Add' 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?

The description gives operational guidance: 'Group Facts for one page in one operation' (batching instruction) and 'do not verify with read or list' (an explicit when-not for named alternatives). But it lacks selection criteria for the primary choice among mutation siblings — an agent is not told when to choose add over create or update for adding facts vs. modifying existing content.

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