Skip to main content
Glama

Read notes

wiki_notes
Read-only

Read notes on a page or subtree.

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>",
      "org": "<org>"
    },
    "name": "wiki_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
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).
subtreeNoInclude notes on descendants.
includeResolvedNoInclude resolved notes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds essentially nothing beyond that: no indication of how many notes a subtree read may return, whether resolved notes are hidden by default (the includeResolved parameter suggests they are), or how note threads are structured. One short sentence, no behavioral context.

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 zero redundant wording. It is efficient, though its brevity comes at the cost of substance rather than being paired with any additional clarifying clause.

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

Completeness2/5

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

For a 4-parameter read tool with no output schema, the description should say at least what a returned note looks like (body, author, resolved state) and whether resolution filtering changes results. It omits both, leaving the agent to discover behavior empirically despite annotations covering only the safety profile.

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%, including the required org slug with its explicit "required on every call" note and the path format with an example, so the schema carries the parameter burden. The description's "page or subtree" loosely gestures at path and subtree but adds no meaning beyond what the schema already documents. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Read notes on a page or subtree" gives a verb (read) and a resource (notes), which is more than a title restatement. But with siblings named wiki_read, wiki_get, and wiki_records, the definition gives no signal for why an agent would pick this tool over those; the only distinguishing hint is "notes," which the agent must interpret unaided.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no when-not-to-use, and no named alternative. The agent is not told whether this is the canonical way to fetch page notes versus wiki_read or wiki_records, nor whether a subtree read is expected to be expensive. Usage must be inferred entirely from the tool name.

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