Skip to main content
Glama

BedrockNews

by com.bedrocknews

get_article

Read-only

Fetch one BedrockNews story by id. Returns the transformed article plus its full structured analysis (GRIN scores, extraction graph, key stats, trajectory, what-to-watch). Pass fields:'grin' to get just the analysis payload without the heavy body text. Story ids contain slashes (e.g. 'ledger/2026/apr/06/iran-war-math-doesnt-work') — pass them verbatim.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe story id, verbatim (ids contain slashes)
fieldsNoOptional projection: 'grin' for the analysis-only view

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate readOnlyHint=true. Description adds rich detail about return payload (GRIN scores, extraction graph, etc.) and optional projection, providing context beyond 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?

Three succinct sentences: purpose, output details, usage tip. No filler, front-loaded with main action.

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?

No output schema, but description fully explains what is returned (transformed article plus structured analysis). Covers all essential aspects for a fetch tool.

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 already describes both parameters (100% coverage). Description adds practical usage details: id must include slashes, fields='grin' for analysis-only view. Exceeds baseline.

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?

Clear verb 'fetch' and resource 'BedrockNews story by id', distinguishes from siblings like get_extraction_graph by specifying it returns the full article plus 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?

Explicitly advises to pass ids verbatim including slashes, and describes optional fields projection. No explicit when-not, but the sibling names imply alternatives for specific sub-tasks.

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

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

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