Skip to main content
Glama

legacy_inspect

Read-onlyIdempotent

Inspect historical SQLite catalogs via a read-only connection and avoid initializing the old controller, enabling safe review of legacy data.

Instructions

Inspect a historical SQLite catalog through a read-only connection; never initialize its old controller.

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

Input Schema

NameRequiredDescriptionDefault
databaseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is known. The description adds real context beyond that: the connection is read-only, the catalog is historical, and the old controller must not be initialized — a non-obvious side effect warning an agent would not get from structured fields. It does not cover error behavior or what happens if the controller is needed.

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?

A single sentence with the operation first and the safety constraint second; no wasted wording.

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?

An output schema exists so return values need no explanation, and the safety constraint is stated. However, with a required parameter undocumented in both schema and description, an agent lacks enough to call it reliably without trial and error.

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?

There is one required parameter, 'database', with 0% schema description coverage, so the description carries the full burden. It says nothing about whether that value is a file path, a DSN, or a catalog identifier, leaving the agent unable to construct the call confidently.

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 verb and resource ('Inspect a historical SQLite catalog') and narrows scope to legacy catalogs, which meaningfully separates it from data_inspect. It does not name or contrast with any sibling tool by name, so differentiation relies on inference from 'historical'.

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?

Implies the target use case (old SQLite catalogs) and gives one hard rule ('never initialize its old controller'), but offers no explicit when-not guidance or named alternative for inspecting a current catalog. The restriction is actionable; routing is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.