NoteMind

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v0.1.0
Disambiguation5/5
Each tool clearly targets either categories or notes, with distinct actions: create/list/delete for categories and add/get/search/suggest/delete for notes. The overlap between get_notes and search_notes is mild and well-defined by keyword filtering. No two tools appear to do the same job.
Naming Consistency5/5
All tool names follow a consistent lowercase snake_case verb_noun pattern, such as create_category, list_categories, add_note, and delete_note_by_text. Minor verb variation between add, create, get, and list is acceptable since the objects and actions remain clear.
Tool Count5/5
Eight tools is a well-scoped set for a note-and-category management server. Each tool covers a distinct operation without unnecessary redundancy or bloat.
Completeness3/5
The server covers create, read, search, and delete operations for both categories and notes, plus a similarity feature. However, there is no update/edit operation for notes or categories, and notes can only be deleted by keyword rather than by a stable identifier, which creates notable lifecycle gaps.
Average 3.8/5 across 8 of 8 tools scored. Lowest: 2.7/5.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 0 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI status not available
Add a LICENSE file by following GitHub's guide. Once GitHub recognizes the license, the system will automatically detect it within a few hours.
If the license does not appear after some time, you can manually trigger a new scan using the MCP server admin interface.
MCP servers without a LICENSE cannot be installed.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of disclosing behavior. It only mentions 'textual similarity' and does not clarify whether the operation is read-only, whether the query is matched exactly or approximately, whether results are ranked, or what the response contains.
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?
The description is a single, efficient sentence with no filler or unnecessary repetition. It is not poorly structured, but it is so brief that it sacrifices useful guidance.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, low parameter clarity, and no usage guidance, the description is incomplete for an agent deciding between this tool and nearby siblings. The output schema may cover return values, but the core invocation semantics are underspecified.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate, but it does not clearly define what the 'query' parameter should contain or how it is used. The phrase 'similar content' implies the query relates to note content, but the mapping is indirect.
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 clearly states the tool's action ('suggest') and resource ('notes with similar content'), and adds the specificity of textual similarity. However, it does not explicitly distinguish the tool from sibling tools like search_notes, so it falls short of 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 Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus search_notes, get_notes, or other sibling tools. Any usage context must be inferred entirely from the phrase 'similar content,' which is too minimal for effective tool selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The phrase 'if it doesn’t exist' discloses conditional creation behavior, which is useful. However, with no annotations, the description does not explain what happens when the category already exists, nor does it mention permissions, side effects, or error behavior.
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?
The description is a single, front-loaded sentence with no filler words. It is concise, though it may be too sparse to fully carry the behavioral and usage guidance an agent needs.
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?
For a one-parameter tool with an output schema, this is nearly adequate, but the duplicate-handling behavior remains ambiguous. The agent must infer whether an existing category causes an error, a no-op, or a returned existing object.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description never directly discusses the name parameter or any constraints. The parameter is implied by the tool name, but the description adds no meaning about uniqueness, formatting, or validation.
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 states the specific operation (create) and resource (category) explicitly, and 'if it doesn’t exist' adds useful idempotency semantics. It is clearly distinguishable from sibling tools like list_categories and delete_category.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no when-to-use or when-not-to-use guidance, and no alternatives are mentioned. The usage context is only implicit, and nothing tells the agent to check list_categories first or explains how this relates to add_note.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. 'Retrieve' signals a read-only operation and 'all notes' discloses the broad, unfiltered-by-default scope. It does not mention pagination, ordering, or category matching behavior, but for a simple read tool these are less critical gaps.
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 concise sentence with the action and resource front-loaded. The parenthetical for the optional category filter is compact and adds relevant information without any filler.
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?
Given the tool is simple with one optional parameter and has an output schema, the description covers the core purpose and parameter role adequately. It is incomplete regarding alternatives like search_notes and the exact value format for category, but it is minimally viable for a straightforward retrieval tool.
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?
The input schema provides zero description coverage for the single 'category' parameter. The description adds the key semantic that category is optional and acts as a filter, which meaningfully supplements the schema. It still does not specify whether category expects a name, slug, or ID, leaving some ambiguity.
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 clearly identifies the action (retrieve) and resource (notes), and specifies the optional category filter. It is easily recognizable as a read/list operation and is distinct from create/delete siblings, though it does not explicitly distinguish itself from search_notes.
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 'Retrieve all notes' implies the tool is for broad retrieval rather than targeted searching, and the optional category filter adds context. However, there is no explicit guidance on when to prefer this tool over search_notes or how category selection relates to list_categories.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It discloses the core containment-matching behavior, but it is silent on case sensitivity, search scope, result ordering, and side effects; the presence of an output schema mitigates some return-value ambiguity.
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 one efficient sentence with no filler, and the main action is front-loaded. It is appropriately short for a one-parameter search tool, even though it achieves brevity by omitting usage nuance.
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?
For a simple tool with one parameter and an output schema, the description is adequate but bare. It lacks explicit routing relative to sibling tools and does not characterize the result set, leaving the agent to infer key contextual details.
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?
The single required parameter 'keyword' is mentioned in the description as the term to search for, adding basic meaning beyond the bare string type in the schema. However, with 0% schema description coverage and no detail on matching rules or accepted formats, parameter semantics are only minimally covered.
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 clearly states the action ('Search'), the resource ('notes'), and the matching criterion ('containing a specific keyword'). It is distinguishable from sibling tools like get_notes and suggest_similar_notes, though it does not explicitly name them.
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 intended use is implied: call this when you need to find notes by keyword. It provides no explicit when-to-use or when-not-to-use guidance and does not contrast with list-like or similarity-based siblings such as get_notes or suggest_similar_notes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It usefully reveals the key side effect—missing categories are created automatically—which is not visible from the schema or tool name. It does not discuss duplication or return behavior, but for a simple add operation the essential behavior is disclosed.
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 with no filler. The main action is front-loaded, and the conditional side effect is given in the second sentence. Every sentence earns its place.
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?
The tool is simple, with two required string parameters and an output schema, so the description does not need to explain return values. It covers the core behavior and the most important non-obvious side effect. A small gap is the absence of explicit guidance for choosing add_note versus create_category, but the auto-create behavior reduces practical ambiguity.
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 0%, so the description needs to compensate. It explains the category parameter's role and implied existence behavior, but it does not explicitly describe the content parameter or its expected format. The parameter names are simple enough that an agent can infer meaning, but the description adds only partial value.
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 clearly states the action (add), the object (a note), and the placement (under a given category), which maps directly to the 'category' parameter. It is easy to distinguish from sibling tools like create_category or delete_note_by_text because it specifically targets note creation.
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 description gives clear context: use this tool to add a note under a category. The auto-creation sentence provides practical guidance that the agent does not need to call create_category first, though it does not explicitly name alternative tools or state when-not-to-use scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It explicitly warns that deletion cascades to all associated notes and that confirm_delete=True is required. It could add irreversibility or permission details, but the core destructive behavior is transparent.
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 concise sentences with no filler. The primary destructive behavior is front-loaded, and the safety requirement is stated immediately after.
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?
The description, combined with the input schema and output schema, gives enough to call the tool: pass the category name and set confirm_delete to true. It does not state what happens when confirm_delete is false, but 'requires' strongly implies no deletion occurs, so this is only a minor 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 0%, so the description must explain parameters. It usefully explains confirm_delete, but it never directly defines the required 'name' parameter; the reader has to infer that 'name' identifies the category from the phrase 'Delete a category.'
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 object: 'Delete a category and all its associated notes.' It clarifies the destructive scope and distinguishes this tool from the sibling delete_note_by_text, which targets individual notes.
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 description clearly conveys when to use the tool: when deleting a whole category and everything tied to it. It also states a key precondition, confirm_delete=True, but does not explicitly name sibling alternatives or exclusion cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden. It discloses an important safety behavior: nothing is actually deleted unless confirm_delete=True, despite the tool's name. It also implies bulk deletion by saying 'notes' rather than 'a note.' It could be more explicit about irreversibility or behavior when confirm_delete is false, but the key destructive guard is revealed.
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 sentences with no filler. The destructive action and the safety gate are front-loaded, and the optional category scoping is included efficiently.
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 destructive tool with no annotations and no per-parameter schema descriptions, the description covers the core semantics and the mandatory safety flag. The output schema presumably covers return values. A small gap is not stating what happens when confirm_delete=False, such as whether it is a no-op or returns matching notes.
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?
Schema description coverage is 0%, so the description must compensate. It does: keyword means 'containing' text, category limits the scope, and confirm_delete controls whether removal actually happens. This adds meaning beyond the bare schema types and defaults.
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 names a specific verb ('Delete') and a specific resource ('notes containing a given keyword'), and adds an optional category scope. This clearly distinguishes it from sibling tools like delete_category and the read-oriented search_notes/suggest_similar_notes.
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 description gives clear context for when the tool is appropriate: deleting keyword-matched notes, optionally filtered by category. It also surfaces the critical prerequisite confirm_delete=True for actual removal. It does not explicitly name alternatives or exclusions, but the keyword-based scope is sufficient for routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. The verb 'List' clearly signals a read-only operation with no side effects, and 'all available categories' states the scope. It does not mention ordering or access nuances, but nothing in the description suggests hidden behavior.
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, compact sentence of five words. It is front-loaded, contains no filler, and does not restate the tool name or schema information.
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 zero-parameter list operation with an output schema, the description is complete. An agent knows exactly how to invoke the tool (empty input) and what it returns conceptually. No additional guidance about pagination or filters is needed because the description says 'all'.
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 input schema is an empty object with 100% coverage, so there is no parameter information for the description to add. The baseline for 0 parameters is 4, which is satisfied because there are no undocumented parameters.
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 states a specific action ('List') and resource ('all available categories'), exactly matching the tool name. It clearly distinguishes itself from sibling write operations like create_category and delete_category, leaving 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 description conveys that this is the tool to use when the agent needs the full set of available categories. It does not explicitly contrast with siblings, but the sibling list shows no other category-listing tool, so the context is clear and no exclusions are needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![notemind-mcpserver MCP server](https://glama.ai/mcp/servers/AdityaTheDev/notemind-mcpserver/badges/card.svg)](https://glama.ai/mcp/servers/AdityaTheDev/notemind-mcpserver)

Score Badge

Copy to your README.md:

[![notemind-mcpserver MCP server](https://glama.ai/mcp/servers/AdityaTheDev/notemind-mcpserver/badges/score.svg)](https://glama.ai/mcp/servers/AdityaTheDev/notemind-mcpserver)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AdityaTheDev/notemind-mcpserver'

If you have feedback or need assistance with the MCP directory API, please join our Discord server