Skip to main content
Glama

Get safety news

get_news
Read-onlyIdempotent

Per-region safety news items, or news for an arbitrary place name.

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_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoPlace name for ad-hoc news, e.g. 'Kelowna'
refreshNoBypass the news cache (API keys with real-time entitlement only)

Output Schema

NameRequiredDescriptionDefault
itemsYes
placeNo
fetchedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / refresh / description
      Previous value: -"Bypass the news cache"New value: +"Bypass the news cache (API keys with real-time entitlement only)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "fetchedAt": {
      +      "type": "string"
      +    },
      +    "items": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "id": {
      +            "type": "string"
      +          },
      +          "image": {
      +            "type": "string"
      +          },
      +          "link": {
      +            "type": "string"
      +          },
      +          "published": {
      +            "type": "string"
      +          },
      +          "region": {
      +            "type": "string"
      +          },
      +          "regionLabel": {
      +            "type": "string"
      +          },
      +          "source": {
      +            "type": "string"
      +          },
      +          "title": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "title",
      +          "link",
      +          "source",
      +          "published"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "place": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "items"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered without the description. The description adds the region-vs-ad-hoc duality, but omits the caching behavior that the schema's refresh parameter alludes to, which is meaningful context for a news tool.

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, so nothing needs trimming. It is efficient, though almost too terse for a tool with a cache-bypass parameter to explain.

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

Completeness3/5

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

Output schema exists, so return values need not be described, and annotations cover the safety profile. What is missing is that place is optional (region defaults) and what the news source/recency characteristics are, which matters for a news tool.

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%, so both parameters are already documented in the schema, establishing a baseline of 3. The description's mention of an 'arbitrary place name' loosely maps to the place parameter but adds no format, limit, or semantics beyond it, and never addresses refresh.

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 description names a specific resource (safety news) and its two retrieval modes: per-region, or by arbitrary place name. That is enough to separate it from read-only siblings like get_incidents and get_trends, though it never explicitly states what distinguishes it from those tools.

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?

It implies two invocation modes but gives no guidance on when to choose news over incidents/trends/crime_year, and no preconditions. The 'or' construction is descriptive rather than prescriptive, leaving the agent to infer selection criteria.

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