Hanging Context: News For Agents

Get new stories since last check

hc_since

Read-onlyIdempotent

Get only the stories that are new since your last call. Send the cursor from the last response. If you send no cursor, the call returns the current cursor and no stories. Returns up to 50 stories with next_cursor and has_more.

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

Input Schema

Name	Required	Description
`limit`	No	Maximum number of results. From 1 to 100.
`topic`	No	Topic id. Call hc_topics for the list. Leave empty for all topics.
`cursor`	No	The next_cursor value from your last hc_since call. Leave empty to get the current cursor.

Output Schema

Name	Required	Description	Default
`count`	No
`error`	No
`reuse`	No
`message`	No
`stories`	No
`has_more`	No
`freshness`	No
`next_step`	No
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

removedOutput schema / properties / from_synorb

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "From Synorb"
-}

Changed1 schema field changedOct 16, 2026
- addedInput schema / required
```
Added value: +[]
```
First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds real behavioral context beyond them: the cursor roundtrip, the 'no cursor = no stories, just a cursor' edge case, and the presence of next_cursor/has_more. Slightly undercut by saying 'up to 50 stories' when the limit parameter allows up to 100.

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 short sentences, front-loaded with the core purpose, then the mechanics. Every sentence carries information; no filler or repetition of the title.

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?

An output schema exists, so return values need not be spelled out, yet the description usefully notes next_cursor/has_more. The only gap is the ambiguous 'up to 50 stories' statement that conflicts with the limit parameter's 1-100 range, which could mislead about result volume.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining cursor semantics — where the value comes from and what happens when it is absent — which the schema only hints at. Topic and limit are left entirely to the schema.

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?

States a specific verb and resource with precise scope: 'Get only the stories that are new since your last call.' The incremental/delta framing clearly distinguishes it from siblings like hc_latest and hc_search without needing to name them.

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 clear operational context: send the cursor from the last response, or omit it to obtain the current cursor. It does not explicitly name an alternative (e.g., hc_latest for a full list) or state when not to use it, so it stops short of full routing guidance.

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

All Hanging Context: News For Agents tools Inspect

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.