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

own-mcp-server

by mayo-byte07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

List Notes

list_notes

Retrieve all saved notes with their ids, titles, and creation times for quick review and management.

Instructions

List all saved notes with their ids, titles, and creation times.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the return fields (ids, titles, creation times) but does not explicitly mention that it is a read-only operation or any other behavioral traits such as authentication or side effects. The read-only nature is implied by 'list', but not stated, leaving room for interpretation.

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 a single sentence with no unnecessary words. It front-loads the action and resource, then lists the returned fields. Perfectly concise and well-structured.

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 simple zero-parameter list tool, the description tells the agent exactly what it returns (ids, titles, creation times) and that it covers all saved notes. There is no output schema, so the description sufficiently covers the return value. No essential information is missing for correct invocation.

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?

The tool has zero parameters, and the schema is trivially covered at 100%. Per the guideline for 0 parameters, the baseline is 4. The description adds no parameter-specific details, but none are needed since there are no inputs.

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 uses a specific verb and resource: 'List all saved notes'. It clearly distinguishes from siblings like add_note, delete_note, calculate, etc., which perform different operations. There is no ambiguity about what this tool does.

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 usage context is clear: it is for retrieving all notes, which is obviously distinct from the sibling tools (add, delete, calculate, etc.). However, it does not explicitly state when to use it over alternatives or any exclusions, but the purpose alone makes the intended usage evident.

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