Skip to main content
Glama
Sign In
teaching-mcp-server

teaching-mcp-server

by DouglasGBailey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get a note by id

get_note

Fetch a note's full title and body by id. Use the id from add_note or list_notes to retrieve saved note content.

Instructions

Fetch the full title and body of one note by its id.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe note id returned by add_note or list_notes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the return payload (title and body), but says nothing about behavior for unknown ids, missing permissions, or whether the fetch is read-only/idempotent. Adequate for a trivial read, but thin.

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?

One sentence, front-loaded with the verb and resource, with zero wasted words while still naming the return payload.

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 one-parameter read tool with no output schema, the description covers what is fetched and what comes back. It is nearly complete, missing only error/absence behavior for an unknown id.

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% and the single id parameter is fully documented in the schema as coming from add_note or list_notes. The description only restates 'by its id', adding no format or validation detail beyond the schema, so the baseline 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 (Fetch), resource (note), scope (one note by id), and what is returned (full title and body). This implicitly distinguishes it from list_notes, but it never names the sibling or explicitly contrast, so it falls short of a 5.

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?

Usage is implied by 'by its id' – reach for it when you have a single id – but there is no explicit when-to-use statement, no mention of when list_notes or read_file would be preferable, and no prerequisite conditions.

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

Deploy Server

Other Tools