Skip to main content
Glama
QueryPilot MCP

QueryPilot MCP

get_definitions

Read-onlyIdempotent

Retrieve business glossary definitions that explain what terms such as revenue mean and what each data column contains; leave the term empty to list all definitions.

Instructions

Business glossary from semantic.yaml: what terms like 'revenue' mean and what each column contains. Leave 'term' empty to get all.

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

Input Schema

NameRequiredDescriptionDefault
termNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds that results come from semantic.yaml, which is mildly useful provenance. It does not describe ordering, pagination, or what happens when a term is not found, so it contributes only modestly beyond the annotations.

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 zero padding; the purpose is front-loaded and the parameter behavior follows. Every clause earns its place and nothing is repeated from structured fields.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies what is needed: what the data is, where it comes from, and what an empty argument does. Only lookup-matching semantics for the term value are left unstated, a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single 'term' parameter only carries a null default, so the description must carry the meaning — and it does: 'Leave term empty to get all' explains the otherwise ambiguous default. It does not indicate matching behavior (exact vs partial/case-insensitive lookup), which keeps it below a 5.

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 names a specific resource — a business glossary sourced from semantic.yaml — and clarifies the two things it covers: term meanings (e.g. 'revenue') and per-column contents. That is far more informative than the bare name. It stops short of explicitly distinguishing itself from siblings like describe_table, which also touches column contents, so it is clear but not fully disambiguating.

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: an agent can infer this is the tool for looking up business-term definitions, and 'Leave term empty to get all' clarifies the broad-listing mode. There is no explicit statement of when to prefer this over describe_table or list_tables, and no exclusions or prerequisites are given.

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