Skip to main content
Glama
Sign In

gol24

by uz.gol24
OverviewDiscussionsAdmin

Latest News

latest_news
Read-onlyIdempotent

Most recent published news from gol24.uz (Uzbek football news site), newest first. Use it for general questions ("what's new in football?", "today's transfer news", "what happened yesterday?"). For one club use club_news, for one person use person_news, for a topic or keyword use search_news. Optional filters: type (transfer, matbuot = press quotes and interviews, natija = final match results, umumiy = other) and date (one calendar day in Tashkent time, YYYY-MM-DD). Filters can be combined. Returns up to limit items (default 10, max 20), each with title and summary in Uzbek (Latin script), url, published_at (Tashkent time), type, clubs and people. An empty list means nothing matched. Rate limit: 60 requests per minute.

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. One calendar day in Tashkent time (UTC+5), format YYYY-MM-DD, e.g. "2026-09-28". Omit for the most recent news.
typeNoOptional. transfer = transfers and rumours; matbuot = press quotes and interviews; natija = final match results; umumiy = everything else. Omit for all types.
limitNoOptional. Number of items, 1-20 (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / date
      Added value: +{
+  "description": "Optional. One calendar day in Tashkent time (UTC+5), format YYYY-MM-DD, e.g. \"2026-09-28\". Omit for the most recent news.",
+  "format": "date",
+  "type": "string"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"How many news items to return (1-20)."New value: +"Optional. Number of items, 1-20 (default 10)."
    • changedInput schema / properties / type / description
      Previous value: -"News type filter. Omit for all types."New value: +"Optional. transfer = transfers and rumours; matbuot = press quotes and interviews; natija = final match results; umumiy = everything else. Omit for all types."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent), and the description goes well beyond them: rate limit (60 req/min), default and max result count, timezone semantics (Tashkent time), empty-list meaning, and the exact shape of returned fields. This is unusually rich behavioral context.

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?

Front-loads the core purpose, then sibling routing, then filters, then return shape and limits. Every sentence carries information an agent needs; no padding.

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

Completeness5/5

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

No output schema exists, but the description compensates by enumerating returned fields, the empty-result case, the rate limit, and default limits. Nothing material to correct invocation 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?

Schema coverage is 100%, so parameters are already documented; the description mainly restates the type enum meanings. It does add genuine value by explaining that the filters can be combined, which the schema does not convey.

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?

States a specific verb+resource+scope ('most recent published news from gol24.uz, newest first') and explicitly differentiates itself from all three relevant siblings by naming the routing rule for each. An agent can select this tool without ambiguity.

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

Usage Guidelines5/5

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

Gives concrete example phrasings of when to use it, then explicitly routes to alternatives: club_news for one club, person_news for one person, search_news for topic/keyword. When-to-use and when-to-use-something-else are both present.

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

All gol24 toolsInspect
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