Skip to main content
Glama

UK motoring news

uk_car_news
Read-onlyIdempotent

Latest UK motoring and automotive news headlines with short summaries and links to the full stories, supplied by Autosnip (FullyAuto). Optionally filter by keyword.

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

Input Schema

NameRequiredDescriptionDefault
limitNo1-20, default 10
queryNooptional keyword, e.g. electric or MOT

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 openWorldHint=false, so the safety profile is covered. The description adds useful context about the upstream source (Autosnip/FullyAuto) and that results include summaries and outbound links, but says nothing about freshness, result ordering, or what happens when the keyword matches nothing.

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 that identifies the content, its shape, and the optional filter with no filler. The parenthetical source attribution is slightly incidental but not wasteful.

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?

For a two-parameter read-only feed tool with full schema coverage and rich annotations, the description covers what the tool returns and how to narrow it. Only minor gaps remain, such as result ordering and behavior on empty matches.

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, including the 1-20 range and default of 10 for limit. The description only restates that filtering by keyword is optional, adding no syntax or matching semantics (e.g. substring vs full-text) beyond the schema.

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 (latest UK motoring/automotive news headlines) and states the payload shape: short summaries plus links to full stories. That clearly separates it from the data-lookup siblings like uk_fuel_prices or mot_statistics, though it never names an alternative explicitly.

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?

It says the keyword filter is optional and gives the flavor of a keyword ('electric or MOT' in the schema), which implies a browse-vs-search usage. There is no explicit when-to-use or when-not-to-use guidance relative to the blog/search siblings.

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