Skip to main content
Glama

sorgu

Run a single read-only SELECT on Istanbul rail ridership data, returning bounded rows and truncation details for analysis.

Instructions

Veri analizi için tek bir SELECT çalıştırın; sınırlı satır ve kesilme bilgisini alın.

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

Input Schema

NameRequiredDescriptionDefault
sqlYes
satir_siniriNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions limited rows and truncation info, but does not disclose permissions, non-SELECT handling, rate limits, or other important operational behavior.

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 with no redundant wording. It communicates the core action and result context efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has two parameters with 0% schema description coverage and no annotations, yet the description does not explain how to use either parameter or when this tool is appropriate. Although an output schema exists, the description leaves key input and usage 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%, so the description should compensate by explaining the sql and satir_siniri parameters. It only implies that sql should be a SELECT and that rows are limited, but does not explain the row limit parameter's name, default, maximum, or interaction with truncation.

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 action: run a single SELECT for data analysis, and notes limited rows and truncation info. It does not differentiate from sibling tools such as sema or istasyon_bul, so it is clear but lacks sibling-level distinction.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives only the broad context 'for data analysis' and does not explain when to use this tool versus alternatives like sema for schema inspection. There are no explicit when-not conditions or prerequisites.

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