Skip to main content
Glama

Kaynakları listele

list_sources

Lists all Turkish data sources available, showing each source's badge, active status, and how to enable key-gated ones, with optional filtering by category.

Instructions

List all Turkish data sources in turkiye-mcp (kaynaklar, rozet: resmî/birinci taraf/topluluk), whether each is active, and how to enable key-gated ones.

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_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault
kategoriNoYalnız bu kategori

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 full burden. It does useful work by disclosing that the response includes active/inactive status and enablement instructions for key-gated sources, and 'List' implies a read-only operation. However, it never states authentication or key requirements for calling the tool itself, rate limits, or result size/pagination.

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?

One compact sentence with the main purpose front-loaded and the detail delivered in a parenthetical. It is dense but every clause contributes; the Turkish term 'kaynaklar' and 'rozet' add minor noise for a non-Turkish reader without much payoff.

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 low-complexity, zero-required-parameter listing tool with no output schema and no annotations, the description covers what the tool returns (sources, badges, active status, enablement hints). The main omission is that it never tells the agent results can be filtered by the 'kategori' parameter.

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

Parameters3/5

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

Schema coverage is 100%, with the single optional 'kategori' enum already documented in the schema ('Yalnız bu kategori'), so the baseline is 3. The description mentions none of the filtering capability — an agent reading only the prose would not know it can narrow results by category such as finans, deprem or hava-cevre.

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 uses a specific verb and resource ('List all Turkish data sources in turkiye-mcp') and adds the scope details of badges (resmî/birinci taraf/topluluk) and active status. It implicitly distinguishes itself from the sibling tools, all of which fetch actual data values rather than enumerate the catalog, though it never names an alternative explicitly.

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 discovery/introspection tool to call before choosing a data-fetching sibling or to find out how to unlock key-gated sources. There is no explicit when-to-use statement, no when-not-to-use, and no named alternatives.

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