Skip to main content
Glama

Write record

wiki_set
Destructive

Write a data record: on a table (a page with a declared key) add or replace the row with that key; on a log add an entry. Read the page's declarations first. To update a row, read it with wiki_get and supply its _v as ifVersion. The result's problems name the links in the record that point at nothing; fix them unless the page they name is about to be written.

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": {
      "path": "<path>",
      "value": "<value>",
      "org": "<org>"
    },
    "name": "wiki_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
tsNoISO-8601 record time for an unkeyed page; defaults to now.
orgYesslug of the organization whose wiki to use. Required on every call, even when only one organization is listed; a path never names it.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).
valueYesThe complete record object, including the declared key field. Must match the page's schema. System fields beginning with _ and pk/sk are reserved.
ifVersionNoExpected existing row version from _v.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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, so the safety profile is covered; the description adds real substance beyond that: replace semantics keyed on a declared key, an optimistic-concurrency contract via _v/ifVersion, and the existence of a problems field in the result naming dangling links. It does not say what happens when ifVersion mismatches (error vs overwrite) or whether the caller needs specific permissions, which are the remaining behavioral gaps for a destructive write.

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, none wasted, with the core write semantics front-loaded before the prerequisite, the update path, and the error-remediation note. Telegraphic phrasing ("point at nothing") is dense but each clause carries distinct 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 destructive 5-parameter write with a nested record object and no output schema, the description covers the essential unknowns: what gets overwritten, how concurrency is checked, and how to interpret the result's failure list. It stops short of describing version-conflict failure behavior and permission requirements, which keeps it from fully complete.

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 100%, so the baseline is 3; the description earns above that by explaining the operational meaning of ifVersion (take _v from a prior wiki_get) rather than merely restating "expected row version". The path/org/value semantics are left entirely to 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?

States a specific verb and resource ("Write a data record") and then splits the resource into its two concrete cases: a keyed table (add-or-replace the row with that key) and a log (append an entry). An agent can tell this is record-level writing rather than page-content writing, but the definition never explicitly contrasts itself with the sibling write tools (wiki_write, wiki_edit), so the boundary is inferred 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit prerequisite ("Read the page's declarations first") and an explicit alternative with its selecting condition ("To update a row, read it with wiki_get and supply its _v as ifVersion"). It also states a conditional exception for remediation ("fix them unless the page they name is about to be written"), which is the kind of when/when-not guidance that actually changes agent behavior.

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