Skip to main content
Glama

news

by media.probable

Put a headline or known source URL in context

get_context
Read-onlyIdempotent

Use when a user supplies a headline or a source URL already observed by Probable and wants same-class context. Optional referenceContext adds explicit country, magnitude, industry or aviation scope for primary-source population references; missingFields and conflicts explain withheld matches. Unknown URLs are not fetched and instead request a headline. Do not use this to verify occurrence, compare unrelated event classes, or forecast.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / anyOf
      Previous value: -[
-  {
-    "properties": {
-      "headline": {
-        "maxLength": 500,
-        "minLength": 8,
-        "type": "string"
-      }
-    },
-    "required": [
-      "headline"
-    ],
-    "type": "object"
-  },
-  {
-    "properties": {
-      "url": {
-        "format": "uri",
-        "maxLength": 2048,
-        "type": "string"
-      }
-    },
-    "required": [
-      "url"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "properties": {
+      "headline": {
+        "maxLength": 500,
+        "minLength": 8,
+        "type": "string"
+      },
+      "referenceContext": {
+        "additionalProperties": false,
+        "properties": {
+          "aviationScope": {
+            "const": "us_scheduled_part121",
+            "type": "string"
+          },
+          "countryCode": {
+            "pattern": "^[A-Z]{3}$",
+            "type": "string"
+          },
+          "industry": {
+            "enum": [
+              "51",
+              "00",
+              "31-33",
+              "44-45"
+            ],
+            "type": "string"
+          },
+          "magnitude": {
+            "maximum": 10,
+            "minimum": 0,
+            "type": "number"
+          }
+        },
+        "type": "object"
+      }
+    },
+    "required": [
+      "headline"
+    ],
+    "type": "object"
+  },
+  {
+    "properties": {
+      "referenceContext": {
+        "additionalProperties": false,
+        "properties": {
+          "aviationScope": {
+            "const": "us_scheduled_part121",
+            "type": "string"
+          },
+          "countryCode": {
+            "pattern": "^[A-Z]{3}$",
+            "type": "string"
+          },
+          "industry": {
+            "enum": [
+              "51",
+              "00",
+              "31-33",
+              "44-45"
+            ],
+            "type": "string"
+          },
+          "magnitude": {
+            "maximum": 10,
+            "minimum": 0,
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "url": {
+        "format": "uri",
+        "maxLength": 2048,
+        "type": "string"
+      }
+    },
+    "required": [
+      "url"
+    ],
+    "type": "object"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive behavior; the description adds meaningful runtime behavior: unknown URLs are not fetched, and missingFields/conflicts explain withheld matches. This is useful context beyond the schema or annotations, though the exact response shape is still only partially described.

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?

Three sentences, with the primary usage front-loaded and the exclusions/edge cases in the final two sentences. No filler or repetition of schema constraints.

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 tool with no output schema, the description covers the key input scenarios, the referenceContext semantics, and the unknown-URL fallback. It leaves the exact notion of 'same-class context' somewhat implicit, but an agent has enough to select and invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already fully describes constraints for headline, url, and referenceContext. The description goes further by explaining what referenceContext does (adds country, magnitude, industry, or aviation scope for primary-source population references) and telegraphs the role of missingFields/conflicts in interpreting results.

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 a specific action ('put ... in context') and resource (a headline or source URL already observed by Probable), and distinguishes itself by explicitly saying not to verify occurrence, compare unrelated event classes, or forecast. This clearly separates get_context from siblings like score_headline or discover_events.

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?

It states the triggering condition ('use when a user supplies a headline or source URL ... wants same-class context') and gives explicit negative guidance (do not use to verify occurrence, compare unrelated event classes, or forecast). It also specifies the unknown-URL fallback behavior, so an agent knows when to request a headline instead.

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

All news toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

The watch and edition tools are clearly distinct, but get_context and score_headline overlap heavily—both accept a headline, share the referenceContext parameter, and disclose withheld/conflicting info—and get_brief vs read_latest_edition both serve 'what's the latest news' requests. The verbose 'do not use for' guardrails in the descriptions help, but they also signal that the boundaries are not naturally obvious.

Naming Consistency4/5

All names follow snake_case verb_noun, with predictable patterns: list_* for collections, create/update/acknowledge for watch mutations, read_* for editions. Minor inconsistency exists between get_brief and read_latest_edition (both fetch news content) and between get_membership and list_watches (both return list-like info), but the overall scheme is readable and consistent.

Tool Count4/5

14 tools sits within the typical well-scoped band, and each tool appears to serve a real product feature. The surface is slightly broad for a 'news' server, spanning saved-watch management, edition reading/export, headline analysis, and membership/checkout, which makes it heavier than a focused news reader.

Completeness3/5

Edition access (list/read/export) and the analysis workflow (score/context/discover) are well covered, but the watch lifecycle has no delete_watch, leaving agents unable to remove saved watches—a real dead end. There is also no story-level read or search tool, though the descriptions explicitly scope that out.

Resources