mcp-server-template

note_set

Save or overwrite a note by specifying a key and value. Useful for managing persistent key-value notes.

Instructions

Save or overwrite a note by key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>",
      "value": "<value>"
    },
    "name": "note_set"
  }
}

Input Schema

Name	Required	Description	Default
`key`	Yes
`value`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits, but it only mentions the action (save/overwrite). It omits details like whether the operation is idempotent, what error conditions exist, or what the response looks like. A mutation tool without annotations requires more context.

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

Conciseness3/5

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

The description is a single sentence, which is concise, but it sacrifices necessary detail. For a tool with only two parameters, it could be slightly longer to include essential parameter behavior without losing conciseness.

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?

Given the lack of output schema, annotations, and parameter descriptions, the description is insufficient to fully understand the tool's behavior, return value, or side effects. The context signaling indicates high complexity due to missing metadata, but the description does not compensate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Both parameters (key, value) have no description in the schema, and the description adds no semantic context beyond 'by key'. The term 'value' is not explained, and key's format or constraints are not clarified, despite 0% schema coverage.

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 ('Save or overwrite') and the resource ('a note by key'), which distinctively sets it apart from siblings like note_delete, note_get, and note_list. The verb-resource pairing is specific and 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?

The description implies that the tool is used for saving or overwriting notes when a key is known, but it does not provide explicit guidance on when to prefer note_set over other tools, such as when to use note_get for reading or note_delete for removal. No when-not-to-use instructions 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