Skip to main content
Glama

Add note

wiki_addNote

Add a note to a page. Each successful call creates a separate note.

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

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.
bodyYesThe note text.
pathYesThe wiki's name, a colon, then the page's dot-separated path (general:docs.deploy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare this is a non-read-only but non-destructive, non-open-world write, so the safety bar is partially covered. The sentence "Each successful call creates a separate note" adds real value by disclosing non-idempotent, append-only semantics with no dedupe or merge. It stops short of stating permission requirements, behavior when the path or page does not exist, or ordering, so it is only partly transparent.

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?

Two short sentences with the action front-loaded and no filler; the second sentence is a genuine behavioral qualifier rather than padding. Slightly more could have been said about alternatives, but nothing present is wasteful.

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?

For a simple three-parameter write tool with full schema coverage, annotations, and no output schema, the description covers the core action and its append semantics adequately. It omits error/failure conditions and any indication of what a successful call returns or how notes are identified afterward, which are the remaining gaps.

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%, with org, body, and path each documented including the required-every-call note and the wiki:page.path format, so the baseline is 3. The description adds no parameter-level meaning (e.g., size limits, path resolution, or whether the page must pre-exist) beyond 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?

"Add a note to a page" gives a specific verb (add) and resource (note on a page), so the agent knows exactly what operation is performed. It does not differentiate against siblings such as wiki_notes, wiki_edit, or wiki_remove, which an agent must distinguish by name alone.

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 explicit when-to-use, when-not-to-use, or alternative routing (e.g., versus reading existing notes with wiki_notes or editing content with wiki_edit). Usage is only implied by the verb "add," leaving the agent to infer the context from the name alone.

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