Skip to main content
Glama

Coline

Show a note

show_note
Read-onlyIdempotent

Opens a note inside the chat as Coline's editor, so the person can read and edit it in place. Use it when the person wants to see or work on a 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": {
      "workspace": "<workspace>",
      "noteId": "<noteId>"
    },
    "name": "show_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYesNote id from search, fetch or create_note.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
urlYes
bodyYes
titleYes
noteIdYes
revisionYes
bodyTruncatedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and non-destructive, so safety is covered. The description adds genuinely new context beyond that: the tool opens an in-chat editor surface where the human reads and edits in place, which explains why a readOnly tool still enables editing. It stops short of describing what happens if the note id is invalid or whether the call blocks.

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, front-loaded with the action and its effect. The second sentence ('use it when the person wants to see or work on a note') largely restates the first, so it earns slightly less than full marks.

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

Completeness5/5

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

A two-parameter, non-destructive UI-opening tool with full schema coverage and an output schema needs little more than what is here: the action, the actor-facing effect, and the trigger condition are all stated.

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 100%, with both workspace and noteId documented in the schema including provenance hints (search, fetch, create_note; workspaces.list). The description adds no meaning beyond that, so the baseline of 3 applies.

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 verb and resource ('Opens a note inside the chat as Coline's editor') and clarifies the effect: the person reads and edits it in place. This distinguishes it from data-fetching siblings like get_note by describing a UI-opening action, though it never names an alternative explicitly.

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?

'Use it when the person wants to see or work on a note' gives a usage condition but is broad enough to overlap with get_note or update_note. There is no exclusion or explicit routing rule telling the agent which sibling to pick when it just needs note content.

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