Skip to main content
Glama
MCP Server Boilerplate

MCP Server Boilerplate

by jeandbonicel

Database

database

Store, retrieve, update, delete, and list JSON values in an in-memory key-value store for the current session. Use it for temporary state and simple data lookups without external persistence.

Instructions

In-memory key-value store. Supports create, read, update, delete, and list operations. Data persists for the session lifetime.

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": {
      "operation": "<operation>"
    },
    "name": "database"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyNoThe key to operate on (not needed for list)
valueNoThe value to store (required for create/update). Can be any JSON value.
operationYesThe database operation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations only give readOnlyHint=false and openWorldHint=false, so the description carries most of the burden. It usefully discloses that storage is in-memory with session-lifetime persistence, which is real behavioral context an agent could not infer from annotations. It omits other important traits: read of a missing key, create on an existing key (overwrite or error), delete of a nonexistent key, and rate/size limits.

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 tightly written sentences with no filler; the core identity (in-memory key-value store) is front-loaded, followed by the supported operations and the persistence caveat. Every clause earns its place.

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 3-parameter CRUD store with no output schema, the description should say what read/list return and how collisions or missing keys behave; those gaps matter for correct invocation. Given rich schema descriptions and safety annotations, the definition is workable but leaves meaningful behavioral questions unanswered.

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%, including notes that key is unnecessary for list and value accepts any JSON and is required for create/update, so the schema already does the parameter work. The description adds no per-parameter meaning beyond restating the operation list, which matches the baseline-3 expectation.

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 resource ('in-memory key-value store') and enumerates the exact operation set (create, read, update, delete, list), so an agent knows precisely what the tool does. It does not explicitly contrast itself with siblings like file-ops or fetch-api, but the resource is distinct enough in practice.

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 operation enum and 'data persists for the session lifetime' hint that this is for transient scratch data rather than durable storage, which does route an agent away from a persistent store. There is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing between operations.

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