Skip to main content
Glama
ThinAirTelematics

ThinAir Data

Official
by ThinAirTelematics
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

optimize_query

Improve SQL query performance by analyzing execution issues and providing rewritten queries, explanations, and index recommendations.

Instructions

Suggest a rewritten, optimized version of a SQL query with explanations. Identifies sequential scans, missing indexes, sort spills, join inefficiencies, and suggests index DDL. [BUILD tier]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • bin/server.js:95-100 (registration)
    Tool registration for 'optimize_query' as part of the static TOOLS array. This is a local reference adapter that only registers tools for listing; actual execution is redirected to the hosted server.
    {
  name: "optimize_query",
  description:
    "Suggest a rewritten, optimized version of a SQL query with explanations. Identifies sequential scans, missing indexes, sort spills, join inefficiencies, and suggests index DDL. [BUILD tier]",
  inputSchema: { type: "object" },
},

Tool Definition Quality

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It describes what issues it identifies and that it suggests index DDL, but does not disclose whether it executes queries or requires permissions, leaving behavioral gaps.

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 concise sentences that front-load purpose and list specific outputs; no wasted words.

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?

No output schema, but description covers return contents (optimized query, explanations, identified issues, index DDL). Could be more explicit about whether the query is actually rewritten or just suggestions.

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?

Input schema has 0 parameters, so baseline is 4. Description adds value by explaining the tool's functionality, though no parameter details are needed.

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?

Description clearly states verb 'Suggest' and resource 'optimized version of a SQL query with explanations', and lists specific issues it identifies, distinguishing it from sibling tools like explain_query and suggest_queries.

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?

Description implies usage for query optimization via '[BUILD tier]' but lacks explicit when-to-use or when-not-to-use guidance, and does not mention alternatives among siblings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ThinAirTelematics/thinair-data'

If you have feedback or need assistance with the MCP directory API, please join our Discord server