Skip to main content
Glama
Sign In
mcp-starter

mcp-starter

by ejoliet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

add_note

Save a note by providing a title and body. This tool stores the note in the notes management system.

Instructions

Save a new note with a title and body.

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": {
      "title": "<title>",
      "body": "<body>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort title
bodyYesNote content

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. It only states 'save a new note,' which implies a write operation, but does not disclose whether updates are possible, if there are limits, or what the response looks like. Behavioral traits beyond creation are missing.

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, front-loaded sentence with no wasted words: action verb 'Save', target 'new note', and parameters 'with a title and body'. Efficient and clear.

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 simple create tool with two parameters and no output schema, the description captures the core functionality. It could optionally mention that it creates a new note (not updates) or hint at the response, but it is largely adequate for the tool's simplicity.

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 coverage is 100% with descriptions 'Short title' and 'Note content.' The description adds marginal value by naming the parameters ('title and body') but does not provide additional constraints or formatting beyond what the schema already offers. Baseline 3 is appropriate.

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?

Description clearly states 'Save a new note with a title and body,' specifying the action (save) and resource (note). It distinguishes from siblings 'delete_note' and 'list_notes' by implying creation vs. deletion and listing.

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 implied (creating new notes), but no explicit guidance on when to use this tool versus alternatives like 'delete_note' or 'list_notes'. No when-not scenarios or prerequisites mentioned.

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