Skip to main content
Glama
mcp-server-starter-sample

mcp-server-starter-sample

by DingXinPro

sqlite_query

Run a parameterized SELECT query against the sample SQLite database to retrieve read-only data. Accepts SQL with optional bound parameters; write operations are not supported.

Instructions

Run a single parameterized SELECT against the sample SQLite database. Writes are not available in this sample.

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": {
      "sql": "<sql>"
    },
    "name": "sqlite_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYes
paramsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the two most important traits: read-only (writes unavailable) and single-statement only. It stops short of covering row limits, result-size caps, statement timeouts, or what happens when the SQL is malformed, all of which matter for a query tool.

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, zero filler, and the capability plus its key restriction are front-loaded. Nothing would be gained by lengthening it in its current form.

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?

The tool is simple (two parameters, no output schema), so the description need not explain return values. However, for an agent to call it correctly it still needs binding syntax and any result-size behavior, and neither is present in the description or the schema.

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 needs to compensate and largely does not. The word 'parameterized' hints that bind values are passed separately, but nothing explains placeholder syntax, binding order, or the 32-item cap on params, leaving both parameters undocumented in prose and schema alike.

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 concrete verb and resource: 'Run a single parameterized SELECT against the sample SQLite database.' The scope qualifiers (single, parameterized, SELECT-only) make the tool's job unambiguous. It does not differentiate from the only sibling, fetch_url, but that sibling is a different domain entirely, so this is a clear-but-not-sibling-aware definition.

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 rather than stated: the 'single' and 'SELECT' constraints plus 'Writes are not available in this sample' tell an agent this is for read-only queries. There is no explicit when-to-use framing, no mention of what to do when a write is needed, and no routing to any alternative for non-SQL retrieval.

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