BedrockNews

list_stories

Read-only

Discover BedrockNews stories with GRIN-aware filters. Filter by verdict ('extractive' | 'mixed' | 'generative'), plumb range (0-100 analytical-clarity score), editorialMode ('grin' news/politics | 'culture' | 'research' | 'ledger'), category (see list_categories), date window (since/before, ISO 8601), or a title search (substring match on titles, not full text). Sorted newest first; paginated via cursor. Returns compact story briefs — use get_article for full analysis.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 15, max 50)
`query`	No	Optional title search (substring match)
`since`	No	Only stories published at/after this ISO 8601 date
`before`	No	Only stories published before this ISO 8601 date
`cursor`	No	Opaque pagination cursor from a previous call
`verdict`	No	GRIN verdict filter, derived from grinScores.extractive
`category`	No	Category id filter (e.g. 'politics', 'research')
`plumbMax`	No	Maximum plumb (0-100)
`plumbMin`	No	Minimum plumb (0-100)
`editorialMode`	No	Filter to one editorial framework

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true, and the description confirms read-only behavior ('discover', 'returns compact briefs'). It also discloses sorting (newest first) and pagination via cursor. No contradictions or missing critical behavioral details.

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 extremely concise (two sentences), front-loaded with the tool's main purpose, and every sentence adds necessary guidance without redundancy.

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?

The tool has 10 parameters (all optional) and no output schema. The description covers filter types, sorting, pagination, and briefly mentions return format ('compact story briefs'). While it could detail returned fields, it is sufficiently complete for a list endpoint.

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%, but the description adds substantial semantic value: explains verdict as GRIN-derived, plumb as analytical-clarity score (0-100), editorialMode options, category referencing list_categories, date ISO 8601, and title as substring match on titles only.

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 clearly states the tool is for discovering BedrockNews stories with GRIN-aware filters, listing specific filter types, sorting, and pagination. It distinguishes from get_article by directing users to that tool for full analysis.

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?

The description provides explicit context for when to use this tool (discover stories with filters) and mentions get_article as an alternative for full analysis. However, it does not explicitly state when not to use this tool, though the purpose is clear enough.

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

All BedrockNews tools Inspect

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

A4.4/5.0

Disambiguation5/5

Each tool serves a distinct purpose: retrieving articles, graphs, related stories, site info, categories, and listing stories. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (get_*, list_*), making the API predictable and easy to navigate.

Tool Count5/5

With 6 tools, the server is well-scoped for a specialized news analysis API. Not too few, not too many.

Completeness4/5

Covers core functionality (listing, retrieving, related stories, metadata). Minor gap: no full-text search, but title search suffices for many use cases.

Resources

Need Help?