Skip to main content
Glama

gol24

News Story

news_story
Read-onlyIdempotent

One gol24.uz news item together with all related items of the same story (every step of a transfer saga, reactions to one match), related items newest first. Use it after latest_news, club_news, person_news or search_news returned an item and the user wants the background or follow-ups. Accepts the item's id, its slug, or the full https://gol24.uz/yangilik/... URL. Returns the item and up to 20 related items with the same fields as latest_news; "related" is empty when the item has no story yet. Returns an error if the item does not exist or is not published. Rate limit: 60 requests per minute.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "news": "<news>"
    },
    "name": "news_story"
  }
}

Input Schema

NameRequiredDescriptionDefault
newsYesThe "id" (e.g. "19176") or "url" of an item returned by another gol24 tool; a slug also works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / news / description
      Previous value: -"News id (e.g. \"19176\"), slug, or full https://gol24.uz/yangilik/... URL."New value: +"The \"id\" (e.g. \"19176\") or \"url\" of an item returned by another gol24 tool; a slug also works."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and idempotentHint; the description goes well beyond them by disclosing the return shape (up to 20 related items, newest first, same fields as latest_news), the empty-'related' edge case, the error conditions (item missing or unpublished), and a concrete rate limit of 60 req/min.

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 what the tool returns, then usage routing, then input forms, then behavioral caveats. Every sentence carries distinct information with no filler.

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?

With no output schema, the description compensates by describing the return payload, its ordering, its empty case, and its failure modes; combined with the rate limit and routing guidance, an agent has everything needed to call it correctly.

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% and the schema description already covers id, url and slug, so the description largely restates the accepted input forms. It adds only the concrete URL pattern example, which is marginal over the schema. Baseline 3 applies.

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 resource (one gol24.uz news item plus its full story thread) and scope (related items newest first), which cleanly separates it from the sibling list/search tools that return single items. An agent can tell immediately that this is a story-expansion tool, not another feed.

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?

Explicitly says to use it 'after latest_news, club_news, person_news or search_news returned an item and the user wants the background or follow-ups' — naming all four alternatives and the trigger condition. Nothing is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources