Skip to main content
Glama
Sign In
AI Notes MCP Server

AI Notes MCP Server

by ibrahimbelkahla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List notes

list_notes
Read-only

Lists saved notes newest first, with optional tag filtering to find relevant entries quickly.

Instructions

List notes, newest first. Optionally only notes with a given tag.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOnly list notes with this tag

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?

Annotations already declare readOnlyHint=true, so safety is covered. The description adds one genuinely useful behavioral fact — results are sorted newest first — but says nothing about result volume, pagination, or truncation, which matters for a list tool that returns everything.

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 short sentences, no filler, with the primary behavior and ordering front-loaded before the optional filter. Every clause carries information.

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-optional-parameter read tool with no output schema and readOnlyHint set, the description covers what the tool does and how it orders results. The absence of any note about result size or pagination is the one remaining gap.

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 description coverage is 100% and the single parameter is already documented as 'Only list notes with this tag'. The description restates that meaning without adding anything new beyond what the schema provides, so 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 and resource ('List notes') plus the ordering ('newest first'), which an agent can act on directly. It does not explicitly distinguish itself from the sibling search_notes, so the boundary between plain listing and searching is left implicit.

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?

The phrase 'Optionally only notes with a given tag' tells the agent that the tag parameter is an optional filter, which implies the basic usage. There is no statement of when to prefer this over search_notes or get_note, so the routing decision is left to inference.

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