Skip to main content
Glama

write_properties

Set or remove structured metadata properties on a LeafWiki page while preserving existing ones, enabling targeted page updates without overwriting other metadata.

Instructions

Set or remove properties (structured metadata) on a page, keeping the others.

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": {
      "page": "<page>"
    },
    "name": "write_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
setNo
pageYesPage id or path
removeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations only declare openWorldHint=false and destructiveHint=false; the description usefully adds the merge semantic that unlisted properties survive, which annotations do not convey. It does not disclose error behavior (e.g., removing an absent key), whether set overwrites existing values, permission requirements, or whether set and remove may be combined in one call. Note a mild tension: the tool 'removes' metadata while destructiveHint=false, though property removal is plausibly recoverable, so this is not treated as a contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with the action and the key semantic constraint in the right order, and no filler. It is compact to the point that the parenthetical '(structured metadata)' is doing the only disambiguation work, but nothing is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, no annotation covering permissions, and two of three parameters are undocumented, so the description carries real weight for a mutation tool. It covers the core merge semantic and the set/remove duality but leaves value types, failure modes, and idempotency unstated — minimally viable rather than complete.

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 coverage is 33% — only 'page' is documented in the schema — and the nested 'set' map and 'remove' array carry no descriptions. The description partially compensates by mapping the two verbs onto the two parameters and clarifying that values are metadata rather than page content, but it never states that set values must be strings, how conflicts are resolved, or that both may be supplied together.

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 pair of verbs (set, remove) and a specific resource (properties/structured metadata on a page), which is enough for an agent to tell this apart from read_properties and from page-body writers like write_edit_text. It stops short of naming or characterizing any sibling, so it lands at 4 rather than 5.

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 phrase 'keeping the others' implies this is the partial/merge path for metadata as opposed to replacing a page wholesale, which is useful implied guidance. However, there is no explicit when-to-use, no mention of when to prefer write_tags or write_update_page, and no stated preconditions, so usage must be inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.