Skip to main content
Glama

Build SQL IN bind parameters

bpj_build_sql_in_parameters
Read-onlyIdempotent

Build an SQL IN clause and separate bind values for SQLite and other drivers using question-mark placeholders.

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": {
      "values": "<values>"
    },
    "name": "bpj_build_sql_in_parameters"
  }
}

Input Schema

NameRequiredDescriptionDefault
valuesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuine behavioral value by disclosing the placeholder style (question marks) and driver scope, but it never says what the returned clause looks like (e.g., '(?,?,?)' vs 'IN (?,?)') or how the bind list is returned alongside it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the action and followed by the concrete driver/placeholder detail. No filler, though the 'SQLite and other drivers' clause could be tightened and space saved for output-format information.

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?

With one parameter and no output schema, the description carries the full burden of describing the result, and it only gestures at it ('clause and separate bind values') without giving the shape or ordering. A single extra sentence about the return value and the JSON-array input format would make it complete; as written it is adequate but leaves real gaps.

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%; the only hint about the single parameter is its title, 'JSON array of strings or numbers'. The description does not explain that 'values' must be supplied as a JSON-encoded array string, what happens with an empty array, or the 6500-character limit — so it fails to compensate for the coverage gap.

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 ('Build an SQL IN clause and separate bind values') plus the placeholder convention used. An agent can immediately tell this is a SQL-fragment construction utility, distinct from the many sibling formatting/analysis tools, though no sibling is named.

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 by the purpose — construct an IN clause before executing a parameterized query — but there is no explicit when-to-use, when-not-to-use, or prerequisite guidance (e.g., 'do not interpolate values yourself'). The only context given ('SQLite and other drivers') is a portability note rather than a routing rule.

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.