Skip to main content
Glama

Resolve note

wiki_resolveNote

Resolve an existing note. Use the ID returned by wiki_notes or wiki_addNote.

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

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).
noteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare a non-destructive, closed-world mutation, but the description adds nothing about what resolving actually changes on the note, whether it is reversible, or what permissions or preconditions apply. For a write operation whose state change is opaque, this is a substantial omission.

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?

Two short sentences, zero filler, with the action stated first and the ID provenance second. Nothing could be removed without losing information.

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?

A three-parameter mutation with no output schema needs the description to explain the resulting state change and any side effects, and it does not. The only behavioral information available is the annotation set, leaving the core semantics of "resolve" undefined.

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 67% and noteId has no description in the schema at all; the description fills exactly that gap by specifying where the ID comes from. The org and path semantics are already handled by the schema, so the remaining value is concentrated where it is needed.

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?

"Resolve an existing note" names a concrete verb and resource, so an agent knows it acts on a single note rather than a wiki or page collection. The weakness is that "resolve" is never unpacked (mark as done? close a thread? delete?), so the effect of the operation stays ambiguous.

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 description only supplies a prerequisite: the noteId must come from wiki_notes or wiki_addNote. It gives no guidance on when resolving is appropriate versus editing (wiki_edit), removing (wiki_remove), or checking (wiki_check) a note, so the agent must infer selection from the verb 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