Skip to main content
Glama

Clipform

by io.github.Clipform
OverviewDiscussionsAdmin

Search News (fallback)

clipform_search_news
Read-onlyIdempotent

Fallback news lookup for clients without native web search. Returns structured current-news articles from NewsAPI and The Guardian.

Coverage: recent events, people, and topics (post-May-2025). Does NOT cover timeless topics (history, geography, science). Narrower and less current than native web search tools (WebSearch, web fetch) when available.

Returns: article title, source, author, date, URL, description, and image URL per result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoMax results per provider (default 5)
queryYesNews search query (e.g. 'Iran war 2026', 'Australian Open final', 'UK election')
contextYesDescribe the user's underlying goal in one sentence - not the tool you're calling.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
articlesYesMatching articles (empty if none)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Describe the user's underlying goal in one sentence - not the tool you're calling.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "query"
-]New value: +[
+  "query",
+  "context"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "articles": {
+      "description": "Matching articles (empty if none)",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "author": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "image_url": {
+            "type": "string"
+          },
+          "published_at": {
+            "type": "string"
+          },
+          "source": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "query",
+    "articles"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only, open-world, and idempotent. The description adds substantial behavioral context beyond that: it returns structured articles from two named providers, covers only post-May-2025 content, excludes timeless topics, and lists the exact response fields. It also warns about being narrower/less current than native web search. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is efficiently structured: the core purpose is front-loaded in the first sentence, followed by clear coverage limitations and a concise return list. Every sentence adds value without repetition or fluff. Despite covering multiple aspects, it remains compact.

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?

Given the three parameters, full schema coverage, rich annotations, and an output schema, the description covers all necessary context: when to use, what it can/cannot find, what providers are used, and the return shape. An agent has everything needed to select and invoke this tool correctly without external references.

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 the baseline is 3. The description does not add parameter-level meaning beyond what the schema provides. It does mention the return data structure, which indirectly helps frame the query, but it doesn't elaborate on 'context' or 'count' beyond the schema's own descriptions.

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?

The description opens with 'Fallback news lookup', specifying the exact verb and resource. It distinguishes itself from sibling search tools like clipform_search_media and clipform_search_music by being news-specific, and explicitly contrasts itself with native web search tools (WebSearch, web fetch). The return fields are listed, making the tool's purpose unmistakable.

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

Usage Guidelines5/5

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

The description states clearly when to use this tool: 'for clients without native web search' and that it is 'Narrower and less current than native web search tools (WebSearch, web fetch) when available.' It also explains coverage boundaries: recent events post-May-2025, not timeless topics. This gives an agent explicit routing criteria.

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

All Clipform toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources