MetalTakip Digest

Günlük piyasa özeti

gunluk_ozet

Read-only

MetalTakip'in son yayımlanan Türkçe piyasa analizini (başlık, özet, bağlantı; otomatik yayın 21 Ekim 2026'da durdu) ve kendi türetilmiş piyasa göstergelerini döndürür. Kaynak atıflı, kişiselleştirilmemiş bilgi.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 25, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already establish that this is a read-only, closed-world operation. The description adds valuable context beyond that: the response is source-attributed, non-personalized, limited to the latest published analysis, and may be stale because automatic publication stopped on a specific date. It could say more about absence/error behavior, but the key behavioral traits are disclosed.

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 compact and front-loaded, starting with what is returned before adding qualification about publication status and information policy. Every clause carries useful information, and there is no redundant restatement of annotations or tool name.

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?

Given that there is no output schema and no parameters, the description does a good job explaining the main return contents and the non-personalized/source-attributed nature of the data. It is slightly incomplete because it does not describe the derived indicators in any detail or specify behavior when no recent analysis exists.

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 has zero parameters, so there is no parameter semantics to document beyond the empty schema. The description appropriately focuses on what the tool returns rather than on nonexistent inputs.

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 clearly states a specific verb and resource: it returns MetalTakip's latest published Turkish market analysis and its own derived market indicators. It also lists the main returned fields (title, summary, link), making the purpose easy to identify. However, it does not explicitly distinguish this tool from the sibling 'turev_gostergeler', which appears related to derived indicators.

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 implied: retrieve the latest published analysis and derived indicators. The note that automatic publication stopped on 21 October 2026 gives useful freshness context. But there is no explicit guidance on when to choose this tool over siblings such as 'fetch', 'search', or 'turev_gostergeler'.

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

All MetalTakip Digest tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?