Skip to main content
Glama

sema

Discover mart table and column schema, data scope, and warnings before querying Istanbul rail ridership data to prepare bounded read-only SQL queries.

Instructions

Veriyi sorgulamadan önce marts tablo ve sütunlarını, kapsamı ve uyarıları öğrenin.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It implies a read-only metadata lookup and tells the agent what categories of information come back (tables, columns, scope, warnings), which is useful. It does not explicitly state that it performs no mutation or how warnings are surfaced, leaving a modest gap for an unannotated tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence with no filler, and the precondition ('before querying data') is front-loaded where it matters most. The only weakness is the slightly generic verb, but nothing is redundant.

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 zero-parameter discovery tool with an output schema, the description only needs to say what metadata it yields and when to call it, and it does both. Return-value details are covered by the output schema, so little is missing.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly does not waste space on parameter explanation.

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 identifies a specific resource set to retrieve: marts tables and columns, their scope, and associated warnings. It signals this is a metadata/schema discovery tool rather than a data-returning query, which distinguishes it from the sibling 'sorgu'. The verb 'learn' (öğrenin) is softer than an explicit 'retrieve'/'list', keeping it just short of a 5.

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?

It gives an explicit trigger: call this before querying data. That directly implies the ordering relationship with 'sorgu'. It stops short of naming the alternative tool or stating exclusions, so it is clear context without full routing guidance.

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