seeds_explain
WHY A POST SCORED WHAT IT SCORED — the honest, checkable breakdown for one post. Pass post_id (the numeric id from any x.com/…/status/<id> link). Returns the exact arithmetic for the rules the post was made under. Posts from 2026-10-02 22:00 UTC use X's own weights (likes x0.5, reposts x1, replie...
This record as markdown: /tools/ai-rokha-rokha/seeds-explain.md
What seeds_explain does on Rokha
AI agents call seeds_explain to retrieve information from Rokha without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
post_id | string | Yes |
Parameters from the server's own tool schema.
Why seeds_explain is rated Low
Tool retrieves and explains scoring calculations for posts; no modifications, no execution, no financial impact.
From the tool's definition breakdown for one post, returns exact arithmetic, checkable scoring rules
Attacks that exploit this kind of access
The rule that runs seeds_explain safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seeds_explain, this is the rule to start with:
seeds_explain is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every seeds_explain call is checked against it from then on.
Questions about seeds_explain
WHY A POST SCORED WHAT IT SCORED — the honest, checkable breakdown for one post. Pass post_id (the numeric id from any x.com/…/status/<id> link). Returns the exact arithmetic for the rules the post was made under. Posts from 2026-10-02 22:00 UTC use X's own weights (likes x0.5, reposts x1, replies x5, quotes x5; seeds = 10 x units, linear, no per-post cap, no tag boost; bookmarks and views carry no weight; then its place in its UTC day: the best 3 earn in full, the 4th min(seeds,100) x0.5, the 5th x0.25, the 6th x0.125, the 7th on 0); older posts show the earlier capped math with its carry. Also: whether RULE ZERO applied (a post nobody engaged with earns NOTHING however many views — the most common reason for a zero), the COPIED check (a word-for-word copy of an earlier post earns x0, with the LINK to the post it duplicated — proven by a duplicate check, never a model judgement), and the final seeds. A post the board never collected is checked LIVE against X: whether X serves it at all (not served = deleted, protected, or withheld — often a spam filter), whether its author is linked, whether it tags us, whether X hides the account from search; a post that belongs on the board is collected on the spot (rate-limited). Public, no auth: a score has to be checkable by the person it was levelled at. It is categorised as a Read tool in the Rokha MCP Server, which means it retrieves data without modifying state.
seeds_explain accepts 1 parameter: post_id. Required: post_id. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for seeds_explain: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rokha. Nothing to install.
seeds_explain is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the seeds_explain rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for seeds_explain. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
seeds_explain is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue