AI Notes MCP Server

Knowledge base statistics

knowledge_stats

Read-only

Retrieve an overview of your knowledge base, including note and tag counts and the most recent activity, to assess what is stored and how current it is.

Instructions

Overview of the knowledge base: number of notes, tags and most recent activity.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 1, 2026

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 the safety profile is covered. The description adds value by enumerating the payload (note count, tag count, recent activity), but it does not define what 'most recent activity' means (timestamp? last N notes?), nor whether counts are exact or scoped to a workspace.

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 sentence of roughly a dozen words with zero filler, leading with the scope ('Overview of the knowledge base') and following with the concrete contents. Nothing is repeated from the title unnecessarily beyond a short 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 tool is simple and parameter-free, and no output schema exists, so the description carries the burden of describing return values — which it only partially does. 'Most recent activity' remains underspecified (a timestamp versus a list of notes), leaving the agent unsure of the response shape before calling.

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 takes no parameters, so there is nothing for the description to disambiguate; the empty schema and the description are consistent. Baseline 4 applies for a zero-parameter tool.

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 names a specific resource (the knowledge base) and a specific kind of output (counts of notes and tags plus recent activity), which clearly separates it from sibling tools like get_note, list_notes, and search_notes that operate on individual or filtered notes. 'Overview' is a slightly loose verb, but the enumerated payload makes the purpose unambiguous.

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 word 'Overview' suggests calling this when a summary is wanted rather than when fetching or searching individual notes. No explicit when-to-use, when-not-to-use, or alternative tool is named, so an agent must infer the routing decision from the sibling names alone.

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

Deploy Server