Skip to main content
Glama
sozcu-mcp

sozcu-mcp

sozcu_market_rates

Fetches Sözcü's live market header quotes—DOLAR, EURO, STERLIN, BITCOIN, ALTIN, FAİZ—with value, change, and change percentage; no arguments needed.

Instructions

Market ticker from Sözcü's page header: DOLAR, EURO, STERLIN, BITCOIN, ALTIN, FAİZ with value, change and change % (TRY, except BITCOIN in USD). No arguments. Values are the site's live header quotes at fetch time.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose useful traits: no arguments are needed, values are the site's live header quotes at fetch time (i.e., a point-in-time snapshot with no history), and units are TRY except BITCOIN in USD. What remains unstated is failure behavior if the site is unreachable, but for a read-only ticker that is a minor gap.

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?

Three short sentences with zero padding: the resource and field list come first, then the no-argument fact, then the freshness caveat. Every sentence carries distinct information an agent can act on.

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 zero parameters and an existing output schema (so return structure needn't be explained), the description covers the essentials: what is returned, in what currency, and how fresh the data is. It stops short of describing error or empty-response behavior, which keeps it just under fully complete.

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 the baseline is 4, and the description explicitly confirms 'No arguments,' removing any doubt about required input. It also clarifies the unit semantics of returned fields (TRY vs USD), which adds value beyond the empty schema.

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?

The description names a specific resource (Sözcü's page-header market ticker) and enumerates the exact fields returned: DOLAR, EURO, STERLIN, BITCOIN, ALTIN, FAİZ with value, change and change %. This is clearly distinguishable from the sibling news tools (headlines, latest, get_article, search_news), none of which cover market quotes.

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?

The description establishes clear context — a no-argument snapshot of live header quotes — which implies the use case (fetch current rates) without spelling out an explicit 'use this when the user asks for currency rates' trigger. Since no sibling covers market data, there is little ambiguity to resolve, but no explicit exclusions or alternatives are stated either.

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