Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

news_get_sources

Read-onlyIdempotent

Retrieve available NewsAPI sources filtered by country, category, or language to identify valid publishers for news queries.

Instructions

Get available news sources from NewsAPI.

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

Input Schema

NameRequiredDescriptionDefault
api_keyNo
countryNo
categoryNo
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. Beyond that the description adds nothing: it doesn't explain that an api_key is typically required by NewsAPI (yet the schema marks nothing required), nor whether filters combine with AND/OR semantics, nor roughly what the response contains.

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?

A single front-loaded sentence with no filler. It is efficient as prose, though the brevity reflects under-specification rather than deliberate terseness.

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

Completeness2/5

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

Four undocumented parameters, no output schema, and no explanation of filtering or auth behavior leave too much unexplained for a tool the agent must call correctly. Annotations cover the read-only nature but not the calling contract.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description mentions none of the four parameters. Critically, api_key is present but declared non-required, and the description offers no hint about when it is needed or how country/category/language narrow the results — the agent gets zero semantics from either source.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource: 'Get available news sources from NewsAPI' tells the agent exactly what is returned (the source catalog, not articles). It does not distinguish itself from the sibling news_top_headlines/news_search tools, but the purpose itself is unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to call this versus news_top_headlines or news_search, which are the obvious siblings. The description also doesn't say whether the country/category/language parameters are filters on the returned source list or something else, leaving the agent to guess.

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

Deploy Server

Other Tools