Skip to main content
Glama

QueryMind

Connect a database

connect_database

Create a secure setup link for the user's business database. Show the link to the user. Credentials must be entered there, never in chat. The link expires in 10 minutes and is single-use. Use a read-only database account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNopostgres, mysql, mssql or oracle; omit if unknown.
nameNoOptional display name for this database.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare the generic safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds genuinely new behavioral facts — 10-minute expiry, single-use link, credentials never handled in chat, read-only account requirement. It does not say what happens after the user completes the flow or whether the tool polls for completion, which keeps it off a 5.

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?

Four short sentences, front-loaded with the action and followed by the operational rules. Nothing is redundant or padded, and each sentence carries a distinct instruction the agent must follow.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two optional parameters, no output schema, and a simple creation flow, the definition covers what the agent needs: what is produced (a link), how to present it, the security constraint, and the link's lifetime. Nothing critical is missing for correct invocation.

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% and both parameters (kind, name) are already documented in the schema, including the 'omit if unknown' hint for kind. The description adds no parameter-level meaning, so the baseline 3 applies; it does implicitly clarify that no credential parameters exist by stating credentials are entered on the link.

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?

The description opens with a specific verb and resource: 'Create a secure setup link for the user's business database.' That is unambiguous and clearly distinct from any sibling in the given catalog (ask, capabilities, invite, usage, etc.), none of which produce connection links.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives concrete operating guidance: show the link to the user, never accept credentials in chat, and use a read-only database account. It stops short of naming when NOT to use this tool or naming an alternative path (e.g., what to do if the user lacks a database), so it is clear context without explicit exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources