Skip to main content
Glama
Sign In
Wenlan

Wenlan

Official
by wenlan-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

page_basis

Idempotent

Track a wiki page’s reliance on another page: mark, confirm, diff, or remove a basis link so changed source notes can be reviewed before the citing page is updated.

Instructions

Track what a wiki page relies on another page for. Use when read_page, list_pages or recall shows a pending basis. mark/confirm need version (the basis note's page.version from read_page) and fail if it moved on. diff shows the text relied on next to the text now. remove drops it. Changes are local stdio only.

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_id": "<page_id>",
      "basis_page_id": "<basis_page_id>",
      "action": "<action>"
    },
    "name": "page_basis"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesmark: record the reliance. diff: show what the basis note said when you last confirmed it and what it says now. confirm: say the page still holds after the basis note's change. remove: drop the reliance.
page_idYesThe page that relies on the other note (the one that would be rewritten or confirmed). Opaque page id.
versionNoRequired for mark and confirm: the basis note's page.version from your read_page (not the citing page's). If the basis note has moved on since, the call is refused and nothing changes. Ignored by diff and remove.
basis_page_idYesThe note it relies on. Opaque page id; never a memory id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.19.3

TDQS

A4/5.0
Behavior4/5

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

Goes beyond the annotations: mark/confirm require `version` and are refused if the basis note moved on ('nothing changes' semantics per schema), remove drops the reliance, and changes are local stdio only. Idempotency and non-destructiveness are already declared by annotations, so no credit there, but the version-refusal behavior is genuinely useful.

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?

Front-loaded purpose, then the trigger condition, then compact per-action clauses. No filler; the telegraphic style stays readable.

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?

There is no output schema, and the description does convey what diff returns ('the text relied on next to the text now'), but it says little about what mark/confirm/remove return or what a pending basis looks like after each action. Adequate for a small 4-param mutation tool but not exhaustive.

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%, and the description's version note ('the basis note's page.version from read_page') largely repeats what the schema already says, including the warning that it is not the citing page's version. Baseline 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?

Opening sentence gives a specific verb and resource: tracking a wiki page's reliance on another page. Implicitly distinguishes from the code-facing sibling page_code_basis by framing it as a text/basis-note relationship, though it never names that sibling.

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?

Explicit trigger: 'Use when read_page, list_pages or recall shows a `pending` basis', and each action word is given a one-line role. It does not say when not to use it or route to page_code_basis for code dependencies, which is the main missing piece.

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