Skip to main content
Glama

Noozra

by com.noozra
OverviewDiscussionsAdmin

Story coverage

story_coverage
Read-onlyIdempotent

Every news site's coverage of one story, newest first: pass the story_id from a latest_news or search_news result to compare how different outlets reported it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoHow many articles to return (1 to 100).
story_idYesA story_id from latest_news or search_news.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesHow many articles are in articles.
articlesYesEvery news site's article on the story, newest first.
story_idYesThe story's id. When the story has been merged into another, the id it is filed under now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "articles": {
+      "description": "Every news site's article on the story, newest first.",
+      "items": {
+        "description": "One article.",
+        "properties": {
+          "category": {
+            "description": "The news section, e.g. world or tech.",
+            "type": "string"
+          },
+          "description": {
+            "description": "The publisher's own short description from its feed; null when the feed has none.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "headline": {
+            "description": "The headline, as the publisher wrote it.",
+            "type": "string"
+          },
+          "id": {
+            "description": "The article's id.",
+            "type": "string"
+          },
+          "published_at": {
+            "description": "When the publisher published it, as an RFC 3339 time in UTC.",
+            "type": "string"
+          },
+          "source": {
+            "description": "The publisher's name.",
+            "type": "string"
+          },
+          "story_id": {
+            "description": "The story the article belongs to: pass it to story_coverage for every news site's coverage. null for an article not yet grouped into a story.",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "description": "The publisher's own article: link this when you show the headline.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "headline",
+          "url",
+          "published_at",
+          "source",
+          "category",
+          "description",
+          "story_id"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "How many articles are in articles.",
+      "type": "integer"
+    },
+    "story_id": {
+      "description": "The story's id. When the story has been merged into another, the id it is filed under now.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "story_id",
+    "count",
+    "articles"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured behavior: results are ordered newest first and the story_id cannot be invented but must be sourced from another tool's output. It does not mention pagination or how partial coverage is handled, 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.

Conciseness5/5

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

A single sentence with zero waste, front-loading what the tool returns and the ordering before the parameter provenance. Every clause earns its place.

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?

An output schema exists, so return structure need not be described. Combined with annotations covering the safety profile and the description supplying ordering plus story_id provenance, an agent has everything needed to call this correctly.

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 coverage is 100%, and the schema's own story_id description already says it comes from latest_news or search_news, so the description largely restates it. The 'compare how different outlets reported it' framing adds intent but no new format or constraint details for either parameter.

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?

Names a specific resource ('every news site's coverage of one story') with a clear verb-like action (compare/report) and states the ordering ('newest first'). It is immediately distinguishable from latest_news and search_news, which produce the story_id this tool consumes.

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

Usage Guidelines4/5

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

Gives explicit provenance: the story_id must come from a latest_news or search_news result, which routes the agent through the correct sibling tools first. It states the use case (comparing how different outlets reported a story) but does not state when not to use it, so it stops short of a full when/when-not rule.

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

All Noozra 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