Skip to main content
Glama

get_note

Retrieve saved notes by exact case-sensitive name to access stored data, reference documents, or session-attached content. Fetches complete note content; provide session_id for session-specific notes.

Instructions

Retrieve a saved note by its exact name.

Fetches the full content of a note previously created with save_note. The name must match exactly (case-sensitive).

Use this when:

  • Retrieving stored data: get_note("api-endpoints")

  • Checking session-attached notes: get_note("findings", session_id="s001")

  • Loading a reference document you saved earlier

If you're not sure of the note name, use recall to search by content or check session context with resume_session.

Args: name: The exact note name used when saving (case-sensitive). session_id: Required if the note was saved with a session_id. Omit for notes saved without a session.

Returns: The full note content. Returns an error if no note exists with that name, or if session_id is required but not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
session_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The get_note tool handler function that retrieves a saved note by name. It accepts a name (required) and optional session_id parameter, then delegates to the _proxy function to forward the call to the remote Astria instance.
    @mcp.tool()
    async def get_note(name: str, session_id: Optional[str] = None) -> str:
        """Retrieve a saved note by its exact name.
    
        Fetches the full content of a note previously created with `save_note`.
        The name must match exactly (case-sensitive).
    
        Use this when:
        - Retrieving stored data: `get_note("api-endpoints")`
        - Checking session-attached notes: `get_note("findings", session_id="s001")`
        - Loading a reference document you saved earlier
    
        If you're not sure of the note name, use `recall` to search by content
        or check session context with `resume_session`.
    
        Args:
            name: The exact note name used when saving (case-sensitive).
            session_id: Required if the note was saved with a session_id.
                Omit for notes saved without a session.
    
        Returns:
            The full note content. Returns an error if no note exists with
            that name, or if session_id is required but not provided.
        """
        return await _proxy("get_note", name=name, session_id=session_id)
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses case-sensitive matching, exact name requirements, error conditions ('Returns an error if no note exists'), and session attachment logic. Would be perfect with explicit statement about read-only nature or side effects, though 'Retrieve' and 'Fetches' imply this.

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?

Front-loaded with clear one-line summary. Uses structured Args/Returns sections which adds slight verbosity but maintains clarity. Every sentence provides value—examples are concrete, constraints are explicit, and no filler text present. Efficient for the amount of information conveyed.

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?

For a 2-parameter tool with flat schema and existing output schema, description is exceptionally complete. Covers success behavior, error states, sibling relationships, session management, and parameter semantics. Exceeds requirements by documenting return values even though output schema exists.

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 has 0% description coverage. Description compensates via Args section explaining 'name' (case-sensitive, exact match) and 'session_id' (conditional requirement based on save context). Deducting one point only because it uses structured docstring format rather than integrated prose, but semantics are fully covered.

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?

Opens with specific verb ('Retrieve') + resource ('saved note') + constraint ('exact name'). Explicitly distinguishes from sibling `save_note` ('previously created with') and contrasts with `recall` ('search by content') and `resume_session` ('check session context'), making selection unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'Use this when:' section with three concrete code examples. Directly addresses uncertainty scenarios ('If you're not sure of the note name') and routes to correct alternative (`recall`). Also specifies prerequisite conditions (session_id requirements) for successful invocation.

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/PL-ODIN/astria-plugin'

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