Skip to main content
Glama

gol24

Person News

person_news
Read-onlyIdempotent

News about one person - player, coach, executive or journalist - from gol24.uz, newest first. Use it instead of search_news whenever the question names a specific person. For a club use club_news. Names on the site are written in Uzbek Latin ("Lamin Yamal", "Kilian Mbappe", "Xansi Flik"); English spellings are matched automatically ("Lamine Yamal" works). Pass the full name: a surname alone is usually not enough. Returns the matched name and up to limit items (default 10, max 20) with the same fields as latest_news. If nobody matches, returns an error - then try search_news with the surname. 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": {
      "person": "<person>"
    },
    "name": "person_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional. Number of items, 1-20 (default 10).
personYesFull name of the person in any common spelling, e.g. "Lamine Yamal" or "Lamin Yamal", "Hansi Flick" or "Xansi Flik".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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 / person / description
      Previous value: -"Full name, e.g. \"Lamine Yamal\" or \"Lamin Yamal\"."New value: +"Full name of the person in any common spelling, e.g. \"Lamine Yamal\" or \"Lamin Yamal\", \"Hansi Flick\" or \"Xansi Flik\"."
  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, but the description adds the rate limit (60 req/min), the error behavior on no match, the automatic English-to-Uzbek spelling matching, and the shape of the response (matched name plus up to `limit` items). That is substantive operational context beyond the annotations.

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?

Front-loaded with purpose and routing, and every sentence carries information (routing, spelling behavior, full-name requirement, return shape, error fallback, rate limit). It is slightly long, with several parenthetical examples that could be trimmed without loss.

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?

With no output schema, the description still explains what comes back (matched name plus items) and defers field details to latest_news, which requires cross-referencing a sibling rather than being self-contained. Error handling, rate limits, and input expectations are otherwise fully covered.

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 the baseline is 3, but the description adds real meaning: it warns that a surname alone is usually not enough, shows Uzbek Latin vs English name forms, and explains that alternate spellings are matched automatically. The only reason it is not a 5 is that the limit bounds it restates are already in the 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?

States a specific verb+resource+scope ('News about one person ... from gol24.uz, newest first') and explicitly distinguishes itself from siblings search_news and club_news. An agent can select it without opening any schema.

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 an explicit routing rule ('Use it instead of search_news whenever the question names a specific person. For a club use club_news') plus a failure-recovery path ('If nobody matches, returns an error - then try search_news with the surname'). Both when-to-use and what-to-do-on-failure are covered.

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