Skip to main content
Glama

Get a note

get_note
Read-only

Fetch a note by ULID, chunk_id, or vault-relative path to get full content, heading outline, or specific chunk, so you can answer with complete context instead of a snippet alone.

Instructions

Fetch the full context behind a search hit before answering from a snippet alone. Fetch a single note by its ULID, indexed chunk_id, or vault-relative path. chunk_id inputs return format='chunk' with the sandbox-wrapped chunk body; a parent-hash mismatch returns an explicit stale-chunk error. Chunk reads ignore offset/limit. For note inputs, format='full' returns the sandbox-wrapped body and offset/limit page large notes by character range; format='map' returns the heading outline only (cheap to scan before requesting full content).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
formatNofull
offsetNo
id_or_pathYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNo
tagsNo
titleNo
formatNo
offsetNo
aliasesNo
contentNo
createdNo
note_idNo
updatedNo
chunk_idNo
headingsNo
line_endNo
rel_pathNo
truncatedNo
line_startNo
chunk_countNo
frontmatterNo
header_pathNo
next_offsetNo
total_charsNo
content_hashNo
limit_appliedNo
next_chunk_idNo
prev_chunk_idNo
returned_charsNo
estimated_tokensNo
note_content_hashNo
chunk_content_hashNo
content_hash_contractNo
returned_estimated_tokensNo
Behavior5/5

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

Annotations already mark this as read-only (readOnlyHint=true), but the description adds substantial behavioral detail: chunk_id returns format='chunk' with sandbox-wrapped body, parent-hash mismatch returns a stale-chunk error, chunk reads ignore offset/limit, and format='full' paginates by character range. This goes far beyond the annotations.

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?

The description is dense but well-structured: purpose, id forms, chunk behavior, then full/map behavior. Every sentence earns its place, and semicolons keep related ideas together. It is appropriately sized for the tool's complexity.

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?

Given the tool's complexity and the presence of an output schema, the description covers all necessary aspects: input types, format behaviors, pagination, and error conditions. It leaves no ambiguity about what to expect, making it complete for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully. It explains the meaning of id_or_path (ULID, chunk_id, path), the format enum values (full, map, chunk), and clarifies that offset/limit page by character range in full format and are ignored for chunk reads. This adds significant meaning beyond the raw schema.

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?

The description clearly states the tool's function: 'Fetch the full context behind a search hit' and 'Fetch a single note by its ULID, indexed chunk_id, or vault-relative path.' This is a specific verb+resource that distinguishes it from siblings like search_text or get_note_history.

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?

The opening sentence gives clear usage context: use this before answering from a snippet alone. It also provides guidance within the tool, such as using format='map' as a 'cheap to scan' option. However, it does not explicitly name sibling alternatives or state when not to use this tool, so it misses the full 'when/when-not' explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/VBlackJack/Datacron'

If you have feedback or need assistance with the MCP directory API, please join our Discord server