Skip to main content
Glama

China News Article

china_news_article
Read-onlyIdempotent

Look up one indexed China/Hong Kong/Taiwan news article by its URL and return everything known about it: publisher, headline, publication time, GDELT theme tags, average article tone and the places it mentions. Pass a url exactly as china_news_search returned it. There is no article text, GDELT indexes metadata only, and this tool says so explicitly rather than returning an empty body field.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "https://english.news.cn/20260911/f8dbbecb7ec349ec979be485497aad96/c.html"
    },
    "name": "china_news_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe article URL, as returned by china_news_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior: there is no article text because GDELT indexes metadata only, which prevents an agent from expecting a body field. It does not cover failure modes such as a URL that was never indexed.

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 the verb and resource, then the return payload, then the caveat about missing article text. The closing clause about saying so 'explicitly rather than returning an empty body field' is slightly self-referential but still conveys a useful expectation, so it mostly earns its place.

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?

For a one-parameter lookup with no output schema, the description enumerates the returned fields and pre-empts the obvious question about article text. Nothing an agent needs in order to call it correctly 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% and the single parameter is documented, so the baseline is 3. The description earns an extra point by adding a real constraint the schema does not: the URL must be passed verbatim as returned by china_news_search, which rules out normalization or guessing.

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 and resource ('look up one indexed China/Hong Kong/Taiwan news article by its URL') and enumerates exactly what comes back: publisher, headline, publication time, GDELT theme tags, tone, places. This clearly separates it from china_news_search, which finds articles rather than fetching one.

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 instruction 'Pass a url exactly as china_news_search returned it' establishes the intended workflow (search first, then fetch) and a hard input constraint. It stops short of stating when not to use it or what happens on a non-indexed URL, so it is clear context without explicit exclusions.

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.