Skip to main content
Glama

Read one published note

get_note
Read-onlyIdempotent

One published note in full: its text as written, the day it was published, its address on the site, and every link it cites. Takes the slug from list_notes or search_notes, or the last part of a note's own URL.

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": {
      "slug": "<slug>"
    },
    "name": "get_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe note's slug, for example "2026-10-28-a-note-title-1a2b3c4d". A full /intel/... path works too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds that this returns the complete note body and all cited links, which is meaningful since no output schema exists, though it says nothing about behavior on an unknown slug or about rate limits.

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 sentences, front-loaded with what the tool is and returns, then the practical sourcing hint for the parameter. No filler wording or repetition of annotations.

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?

For a single-parameter read tool with full annotations, the description covers purpose, inputs, and return contents adequately. Only error/empty-result behavior is unaddressed, a minor omission given the simple shape.

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 100% and includes a concrete slug example, so the baseline is a 3. The description adds provenance — that the slug comes from list_notes, search_notes, or the tail of a note URL — which is meaning beyond the schema's format constraints.

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

Purpose5/5

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

States a specific verb and resource (read one published note in full) and enumerates what comes back: text as written, publication date, site address, and every cited link. This clearly separates it from the sibling list_notes and search_notes, which are referenced by name.

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?

Explains where the required value comes from — the slug from list_notes or search_notes, or the trailing segment of a note's own URL — which is explicit input-sourcing guidance. It does not spell out when not to use it (e.g. use search_notes for full-text lookup across notes), leaving a small gap.

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