Skip to main content
Glama
Sign In
GetNote MCP Server

GetNote MCP Server

by iswalle
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_topic_notes

List accessible notes in a knowledge base with filters for source, reference resources, and time. Returns locator info only; paginate results to browse further.

Instructions

列出知识库内可访问的笔记，支持来源、引用资源、时间筛选。列表只返回定位信息；需要正文和完整元数据时调用 get_note。按 pagination.next_page 翻页；去重 ID，重复游标/页码、无进展或中途失败不能声称全量完成。

Input Schema

NameRequiredDescriptionDefault
pageNo页码，从 1 开始（默认 1）
sourceNo笔记真实来源精确筛选：vendor_moan=AI录音台/墨案MOAN录音台，getseed=GetSeed录音卡（长录音与闪念），dedao=得到。查设备全部笔记只加来源，不额外限定audio/meeting；未限定设备时不加设备来源。
topic_idYes知识库 ID
edited_toNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
note_typeNo真实类型精确筛选：ref=引用划线，audio=即时/普通录音，local_audio=上传音频文件，class_audio=自己录制的课堂笔记，meeting=会议，internal_record=内录，recorder_audio/recorder_flash_audio=录音卡长录音/闪念。录音不默认限定dedao或课程。
page_sizeNo每页 1–100 条，默认 20
created_toNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
edited_fromNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
created_fromNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
record_updated_toNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
record_updated_fromNoRFC3339 带时区，from 包含、to 不包含；三种时间轴独立
reference_course_idNo真实课程容器ID字符串，来自list_reference_resources；不使用课节resource_id替代
reference_article_urlNo文章 URL 精确筛选，保留 query 和 fragment
reference_course_typeNo课程容器类型，当前66；与reference_course_id配对，source=dedao，个人笔记，不与topic_id组合
reference_resource_idNo引用资源 ID，必须字符串；同时传 source 和 reference_resource_type
reference_resource_typeNo引用资源类型，如 ebook、course_article、audio_book

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.10.1
    • addedInput schema / properties / created_from
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / created_to
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / edited_from
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / edited_to
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / note_type
      Added value: +{
+  "description": "真实类型精确筛选：ref=引用划线，audio=即时/普通录音，local_audio=上传音频文件，class_audio=自己录制的课堂笔记，meeting=会议，internal_record=内录，recorder_audio/recorder_flash_audio=录音卡长录音/闪念。录音不默认限定dedao或课程。",
+  "type": "string"
+}
    • addedInput schema / properties / page_size
      Added value: +{
+  "description": "每页 1–100 条，默认 20",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / record_updated_from
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / record_updated_to
      Added value: +{
+  "description": "RFC3339 带时区，from 包含、to 不包含；三种时间轴独立",
+  "type": "string"
+}
    • addedInput schema / properties / reference_article_url
      Added value: +{
+  "description": "文章 URL 精确筛选，保留 query 和 fragment",
+  "type": "string"
+}
    • addedInput schema / properties / reference_course_id
      Added value: +{
+  "description": "真实课程容器ID字符串，来自list_reference_resources；不使用课节resource_id替代",
+  "type": "string"
+}
    • addedInput schema / properties / reference_course_type
      Added value: +{
+  "description": "课程容器类型，当前66；与reference_course_id配对，source=dedao，个人笔记，不与topic_id组合",
+  "type": "string"
+}
    • addedInput schema / properties / reference_resource_id
      Added value: +{
+  "description": "引用资源 ID，必须字符串；同时传 source 和 reference_resource_type",
+  "type": "string"
+}
    • addedInput schema / properties / reference_resource_type
      Added value: +{
+  "description": "引用资源类型，如 ebook、course_article、audio_book",
+  "type": "string"
+}
    • addedInput schema / properties / source
      Added value: +{
+  "description": "笔记真实来源精确筛选：vendor_moan=AI录音台/墨案MOAN录音台，getseed=GetSeed录音卡（长录音与闪念），dedao=得到。查设备全部笔记只加来源，不额外限定audio/meeting；未限定设备时不加设备来源。",
+  "type": "string"
+}
  2. First observedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that results are location-only, how to paginate, that IDs must be de-duplicated, and that repeated cursors/pages, no progress, or mid-way failure must not be reported as complete. It omits permission/rate-limit context, which is minor for a read listing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three compact sentences, front-loaded with what is listed and what is returned, then the alternative, then pagination/result-integrity caveats. Dense and largely waste-free, though the final clause is telegraphic.

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 16-parameter read tool with no annotations and no output schema, the description supplies the missing return-shape context (locating info only) and pagination/completeness semantics. Only the absence of output-schema-like detail on the result fields keeps it from a 5.

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 the schema already documents all 16 parameters, including the cross-parameter pairing rules (source + reference_resource_type) and the independent time axes. The description only restates the filter categories at a high level, adding little beyond the schema, which fits the baseline 3.

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+resource ('列出知识库内可访问的笔记') and names the filter axes (来源、引用资源、时间). It also distinguishes itself from get_note by saying the list returns only locating info, though it doesn't explicitly separate itself from the sibling list_notes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool (locating notes with source/reference/time filters) and when to use an alternative ('需要正文和完整元数据时调用 get_note'). The pagination instruction ('按 pagination.next_page 翻页') further constrains usage.

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