NoteKing MCP

noteking_list_notes

Retrieve NoteKing notes with full-text search and filters for project, standalone scope, and pinned status, so you can find relevant developer notes and ADRs.

Instructions

List, filter, and search notes in NoteKing by full-text query, project, standalone scope, or pinned status

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": "noteking_list_notes"
  }
}

Input Schema

Name	Required	Description
`q`	No	Full-text search query across note title and Markdown body
`limit`	No	Number of notes to return (default 50, max 100)
`scope`	No	Scope filter: 'standalone' (unassigned scratchpad notes) or 'all'
`offset`	No	Pagination offset (default 0)
`pinned`	No	Filter by pinned status (true = only pinned, false = only unpinned)
`project_id`	No	Filter notes belonging to a specific project ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 14, 2026

TDQS

B3.3/5.0

Behavior2/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, yet it discloses nothing beyond the filtering concept. It does not state that results are paginated, what the default page size or ordering is, whether a total count is returned, or how the filters combine when several are supplied — all relevant for a 6-parameter list endpoint.

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?

A single front-loaded sentence with the verb and resource first and the filter axes enumerated after; there is no filler or redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The input schema is fully self-documenting and no output schema exists, so the description need not explain return fields. However, for a paginated list tool with zero annotations, it should at least indicate ordering or result-set behavior; that omission leaves it only minimally complete.

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%, so every parameter (q, limit, offset, scope, pinned, project_id) is already documented with defaults and bounds in the schema. The description merely names the same filter dimensions again, adding no syntax, format, or combination semantics beyond the schema.

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?

The description states specific verbs (list, filter, search) and the resource (notes in NoteKing), plus the four filter axes, so an agent can immediately tell this is a read-only collection query. It does not distinguish itself explicitly from the sibling noteking_get_note (single-note retrieval), leaving that gap at a 4 rather than 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 only implied: the enumerated filter axes (full-text query, project, standalone scope, pinned) hint at when the tool is appropriate, but there is no statement of when to prefer it over noteking_get_note or noteking_list_projects, and no preconditions or exclusions are given.

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

Deploy Server