Skip to main content
Glama

get_iceland_news

Read-onlyIdempotent

Get recent Iceland news headlines from Icelandic publishers.

Each article names its publisher, such as mbl.is (Morgunblaðið), The Reykjavík
Grapevine or Iceland Review, and gives the headline, a short summary, a link to
the full article on the publisher's site, and the publication date. Sóley only
gathers the publishers' RSS feeds: whenever you use an article, name its
publisher (for example "according to mbl.is") and include the article's own link.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of articles to return (1–25).
categoryNoNews category filter.all
languageNoResponse language: 'en' for English, 'is' for Icelandic.en

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses data provenance ('Sóley only gathers the publishers' RSS feeds'), which tells the agent summaries are feed-level and full text lives off-site, plus a licensing/attribution obligation. No rate limits or pagination behavior are mentioned, keeping it below a 5.

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?

Two short paragraphs, front-loaded with the purpose before the return shape and the attribution rule. The parenthetical publisher examples (mbl.is, The Reykjavík Grapevine, Iceland Review) are slightly decorative but do illustrate the publisher-naming requirement, so they largely earn their place.

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?

An output schema exists, so the description's field listing is a bonus rather than a necessity, and the provenance and attribution notes cover the non-obvious risks of this read-only tool. Nothing essential is missing, though a note on freshness or how many sources are aggregated would have closed the gap.

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 description coverage is 100% with two enum fields, so limit, category and language are already fully documented in the schema. The description adds no meaning about defaults, enum trade-offs, or how 'all' interacts with the topic categories, so it sits at the baseline.

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?

The opening sentence gives a specific verb and resource ('Get recent Iceland news headlines from Icelandic publishers') and the second sentence enumerates the returned fields, so the agent knows exactly what it gets. It falls short of a 5 only because it never distinguishes itself from topical siblings like get_safety_alerts or get_weather, even though the schema exposes 'safety' and 'weather' news categories that could overlap.

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

Usage Guidelines3/5

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

There is no explicit 'use this when...' framing, no exclusions, and no routing advice against the safety/weather tools that share its category vocabulary. The one genuine usage rule it does give is mandatory attribution ('whenever you use an article, name its publisher'), which is a downstream obligation rather than a selection guideline.

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