Skip to main content
Glama
Sign In
drill-mcp

drill-mcp

Official
by apache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_profiles

Retrieve recent and running Apache Drill query profiles, newest first, and control the result count with an optional limit.

Instructions

List recent and running query profiles, newest first.

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

There are no annotations provided, so the description carries the burden. It discloses that results are sorted newest first and are limited to recent and running profiles. However, it does not disclose whether this requires specific permissions, whether it's read-only (though list implies), or any pagination behavior. Minimal but not misleading.

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?

The description is a single front-loaded sentence: 'List recent and running query profiles, newest first.' It conveys purpose, scope, and ordering with no wasted words.

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?

The tool is simple with one optional parameter and an output schema, but the description is minimal. It covers purpose and ordering, but lacks parameter semantics and usage guidance compared to alternatives. Given the complexity, the description has some gaps but is minimally viable.

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?

The schema has one parameter 'limit' with a default of 20, and schema description coverage is 0%. The description does not mention the limit parameter at all, forcing the agent to infer its semantics from the parameter name. This is a gap, though the parameter name is simple.

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 uses the specific verb 'List' and clearly identifies the resource as 'query profiles', with qualifiers 'recent and running' and ordering 'newest first'. This distinguishes it from siblings like get_profile (specific profile) and cancel_query.

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?

The description states what the tool does but provides no explicit guidance on when to use it versus alternatives like get_profile. Usage is implied by the name and description, but no exclusions or alternatives are mentioned.

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

Deploy Server

Other Tools