Skip to main content
Glama
Sign In
db-conn-mcp

db-conn-mcp

by Idle-Sync
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

close_cursor

Close an open cursor and release its database connection to free resources; repeat calls are safe because the operation is idempotent.

Instructions

Close an open cursor and release its database connection. Idempotent.

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": {
      "cursor_id": "<cursor_id>"
    },
    "name": "close_cursor"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does contribute real behavior: the connection is released and the call is idempotent, which tells the agent repeated calls are safe. It omits what happens to unfetched rows, whether an invalid or already-closed cursor_id errors, and whether the connection returns to a pool.

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 short sentences with the effect stated first and the idempotency guarantee second; nothing is padded and no sentence is wasted.

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 one-parameter cleanup tool with no output schema and no annotations, this covers the essential contract: what it does, what it frees, and that repeats are safe. Only edge-case behavior for stale or invalid cursor ids is missing.

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 0% for the single required parameter, so the description must compensate. It implies the identifier refers to a cursor created by open_query_cursor, but never states the expected format or what happens if the id is unknown, leaving the parameter largely documented only by its name.

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 ("Close an open cursor") plus the effect ("release its database connection"), which clearly separates it from open_query_cursor and fetch_rows in the sibling list. It stops short of naming the sibling it complements, so it is clear but not maximally differentiated.

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 agent must infer that this is the cleanup step after open_query_cursor/fetch_rows. There is no explicit when-to-use statement and no guidance on choosing it over cancel_query, which is a plausible alternative for an in-flight query.

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

This server cannot be deployed

Other Tools