Skip to main content
Glama

Query data

query_data
Read-onlyIdempotent

Run bounded, read-only parameterized SQL against the curated Ubi Data API. Mutating SQL is rejected.

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": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYesSQL query with ? placeholders for user values (DuckDB dialect).
paramsNoValues to bind to ?-placeholders, in order. Default: [].

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered structurally. The description still adds real value beyond them by flagging 'bounded' (queries are constrained in cost/scope) and the rejection of mutating SQL, which tells the agent failures will occur on writes. It does not quantify the bound (row caps, timeouts) or say which curated tables are reachable, leaving some behavioral detail unstated.

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, both of which earn their place: the first defines the capability and its constraints, the second states the hard exclusion. The constraint and the rejection rule are front-loaded with no filler.

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?

An output schema exists, so return values need no explanation, and the two parameters are fully documented in the schema. The remaining gap is qualitative: an agent is told the query is 'bounded' without knowing the row/time limits or whether the curated tables must be discovered first, which matters for a free-form SQL entry point.

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 100%: the sql parameter already documents ? placeholders and DuckDB dialect, and params documents ordered binding with a default. The description only reinforces 'parameterized' generically, adding no dialect, binding, or value-type detail beyond the schema, so the baseline 3 applies.

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?

The description states a specific verb (Run) and resource (parameterized SQL against the curated Ubi Data API) with an explicit scope (bounded, read-only), which clearly separates it from catalog/describe siblings such as describe_table or search_catalog. It stops short of naming any sibling, but the 'arbitrary read-only SQL' framing is distinctive enough for an agent to select it confidently.

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?

'Read-only' and 'Mutating SQL is rejected' give a clear when-not condition, and 'parameterized' implies values should be passed via binds rather than interpolated. The description however never points to alternatives (e.g., describe_table for schema discovery, search_catalog for exploration) when ad-hoc SQL is the wrong choice, so it falls short of a full use-this-vs-that guide.

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