baba News by baba Hebrew

Every article in a cluster, paged

stories_members

Read-only

Every article in a cluster, paged. The same member records /v1/stories/{ckey} returns, but paged and filterable by side or lean. side and lean come from the source registry rather than the row, so a filtered page can be shorter than its limit while still issuing a cursor. Requires the stories API scope. English is the fallback for untranslated fields.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ckey`	Yes
`lang`	No	Output language. Hebrew falls back to English per field when a row is missing.	en
`lean`	No	Only members with this political lean. Unknown values are 400.
`side`	No	Only members from this group. Unknown values are 400. The old values religious, russian and business are accepted as right, other and other.
`limit`	No	Page size. Non-integer or negative values are 400; values above 100 are clamped to 100 and echoed as page.limit.
`cursor`	No	Opaque keyset cursor from a previous page nextCursor. Malformed values are 400.

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: -"Only members from this camp. Unknown values are 400."New value: +"Only members from this group. Unknown values are 400. The old values religious, russian and business are accepted as right, other and other."

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

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: requires the stories API scope, discloses that side/lean are resolved from the source registry so a filtered page can be short yet still return a cursor, and states the English fallback for untranslated fields. These are non-obvious operational facts an agent needs.

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 tight sentences, front-loaded with the core purpose and followed by the operational caveats. Slight redundancy with the lang enum description restating the English fallback, but no wasted sentences.

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?

With annotations covering safety, an output schema covering returns, and 83% schema coverage, the description supplies exactly the missing pieces — auth scope and filter/pagination quirks — so an agent can invoke it 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?

Schema coverage is 83% and already documents each parameter well, so the baseline is 3. The description adds value beyond the schema by explaining the filter-resolution nuance (registry vs row) that affects cursor/pagination behavior.

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 resource (every article/member in a cluster) and a specific mode (paged), and explicitly ties it to the sibling endpoint /v1/stories/{ckey} so an agent can distinguish it from stories_get and stories_list.

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?

Implies when to use it — when you need the member records paged or filtered by side/lean rather than the unpaged story endpoint. It gives clear context but names no explicit exclusion beyond the comparison to /v1/stories/{ckey}.

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.