Compare two listings on the same axes
onchain_agent_compare_listingsUSE WHEN the question is how two directory listings compare on the axes Sato Hub tracks for both (ANSWERS ONE QUESTION), e.g. "AgentKit or Solana Agent Kit?". NOT FOR a single project's detail (use onchain_agent_get_resource instead) or a ranked stack for a goal (use onchain_agent_recommend_stack).
RETURNS the SAME derived table the /compare pages render — category, chains, interfaces, standards, open-source status, listing status, last activity, last release, install proof, verification, Sato Score, GitHub stars — every cell read off the live records, never typed.
RULE ENFORCED: there is NO winner field and none can be derived from the table; caveat is mandatory and names what the data cannot settle (for a curated pair, the comparison page's own caveat). The Sato Score is openness/activity/verifiability, not a safety, quality or returns grade.
RETURNS (json): { a: { slug, name, liveness, observed_success_pct, sato_url }, b: {...}, rows: [{ label, a, b, note? }], caveat, rules, comparison_page, source }. Read-only.
Example: { a: "coinbase-agentkit", b: "solana-agent-kit" }
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"a": "<a>",
"b": "<b>"
},
"name": "onchain_agent_compare_listings"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| a | Yes | First directory slug, e.g. 'coinbase-agentkit'. | |
| b | Yes | Second directory slug, e.g. 'solana-agent-kit'. | |
| response_format | No | Text format; structuredContent is JSON either way. | markdown |