baba News by baba Hebrew

Coverage gaps, by camp

blindspots_list

Read-only

Coverage gaps, by camp. Requires the stories API scope. English is the fallback for untranslated fields.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Output language. Hebrew falls back to English per field when a row is missing.	en
`side`	No	Return only stories the named group did not run. Unknown values are 400. Since 2026-10-01 the press is read in five groups (left, centre, right, haredi, arab), with the outlets outside them as other; the old values are still accepted as the group they became: religious as right, russian and business as other. Other is never missing, so other, russian and business return no stories.
`limit`	No	Page size. Non-integer or negative values are 400; values above 100 are clamped to 100 and echoed as page.limit.
`state`	No	Repeatable. Unknown values are 400, unlike on /v1/stories, because this resource is only about these two.
`cursor`	No	Opaque keyset cursor from a previous page nextCursor. Malformed values are 400.
`window`	No	How many minutes back to consider a state row current, 15-10080. Values below 15 are raised to 15; above 10080 are clamped.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / side / description

Previous value: -"Return only stories the named camp did not run. Unknown values are 400."New value: +"Return only stories the named group did not run. Unknown values are 400. Since 2026-10-01 the press is read in five groups (left, centre, right, haredi, arab), with the outlets outside them as other; the old values are still accepted as the group they became: religious as right, russian and business as other. Other is never missing, so other, russian and business return no stories."

changedInput schema / properties / side / enum

Previous value: -[
-  "left",
-  "centre",
-  "right",
-  "haredi",
-  "religious",
-  "arab",
-  "russian",
-  "business",
-  "official"
-]New value: +[
+  "left",
+  "centre",
+  "right",
+  "haredi",
+  "arab",
+  "other",
+  "official"
+]

First observedSep 26, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts not in annotations: the required stories API scope and the English fallback for untranslated fields. It stops there, adding nothing about pagination, result ordering, or what a gap row contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Three short sentences with no filler. The scope requirement and fallback note are front-loaded. The one weakness is that the leading sentence is a title restatement that spends space without conveying the action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be explained, and the scope/fallback notes cover the key operational facts. But for a 6-parameter read tool with a non-obvious 'camp blindspot' concept, the description leaves the core semantics (what a blindspot row means, how state and side interact) to the schema.

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 description coverage is 100%, so the schema already documents every parameter in detail (side enum remapping, limit clamping, state repeatability, cursor format, window bounds). The description adds no parameter meaning beyond the fallback-language note, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Coverage gaps, by camp" names a resource-ish concept but never states a verb or action, and it merely restates the title verbatim. It doesn't distinguish the tool from siblings like stories_list or trending_list. The schema (state enum with blindspot/undercovered, side enum) reveals the real purpose more than the description does.

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

Usage Guidelines2/5

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

No guidance on when to use this versus stories_list or search_list, and no mention that state/side combinations drive the query. The 'Requires the stories API scope' note is an access prerequisite rather than usage guidance.

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

All baba News by baba Hebrew 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.