Loading ToolBench
Catch the MCP server that changed after you trusted it — local-first provenance, drift detection, revocation, policy, and stack management across every agent host.
Agora-hub exhibits significant definition quality gaps. Tool naming is inconsistent (agora_search appears twice with different schemas; agora_acquire and agora_browse duplicated). Descriptions vary widely in quality, some are detailed (agora_stack_status at ~200 chars), others are vague (agora_today, agora_info). Input schemas are present but incomplete: many parameters lack type constraints (e.g., agora_search 'source' enum is well-defined, but agora_today 'section' lacks validation). Output schemas are entirely undocumented, no tool specifies what fields are returned. Error handling is absent from all tool definitions. Parameter descriptions are sparse or missing context (e.g., 'Section to show' without explaining what data is returned). The server conflates CLI mirroring with agent-friendly tool design, tools like agora_plan expose internal concepts (scope, prune) without explaining their impact on the user's workflow.
Preview acquiring a capability through the scan-gated Agora installer. Unconfirmed calls preview; the retained `confirm` field creates an inert install intent for human review and never edits the stack.
Preview acquiring a capability through the scan-gated Agora installer
Browse an individual package or workflow with full details
Full merged catalog item detail, including trust-panel data: a fresh scan-gate verdict, official-registry status, and any trust record from a prior `agora_acquire`. Resolves against the same catalog sources the CLI `agora browse` uses.
Browse packages and workflows by category
Check your OpenCode config health and list the repairs it needs. This tool never edits the config: an agent cannot authorize a host-configuration write, so `fix` reports the exact changes for a human to apply with `agora config doctor --fix`.
Show information about Agora plugin
Duplicate tool definitions across CLI and plugin variants (agora_search, agora_browse, agora_acquire appear 2-3 times with inconsistent schemas). LLMs will be confused about which variant to call and may select the wrong one.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., what does agora_search return? Is there a 'server_id' field for chaining to agora_browse?). This violates the response-shaper pattern.
Parameter descriptions are minimal or missing context. 'Section to show: news, market, or all' (agora_today) does not explain what data is returned or when to use each section. 'Category: mcp, prompt, skill, all' (agora_browse_category) lacks guidance on the difference between these categories.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 56 | 2026-07-28+ | v2 |
Generate install steps for a package or workflow
Read-only diff between agora.toml and the real MCP config / instruction files of every detected agent tool. Never writes anything. `from` previews a shared profile (git url, gist, or path) and runs the same scan gate `agora sync --from` runs before diffing — a hard fail short-circuits to a gate-blocked result. Mirrors `agora plan --json`.
Scan an Agora item for trust and install-risk signals
Search the Agora catalog for MCP servers, packages, and workflows
Search the multi-source MCP catalog (official MCP Registry + local bundled catalog, deduped across sources) for MCP servers and Agent Skills. Mirrors `agora search --json`.
Doctor summary of the user's configured MCP stack across opencode/Claude Code/Cursor/Windsurf: per-server static health (command resolvable, valid remote url, disabled, conflicting definitions) plus discovered tool capabilities from the local probe cache. Static checks only — never starts servers (use `agora doctor --probe` in the CLI for that). Mirrors `agora doctor --json`, enriched with each server's cached tool list.
Show today's Agora news and catalog highlights
No error handling guidance in any tool definition. If agora_search returns no results, or agora_acquire fails a scan gate, the LLM has no recovery path. Missing recovery-guide pattern.
agora_info has a trivial description ('Show information about Agora plugin') and empty input schema. This tool is not actionable for an LLM, it provides no context for when or why to call it.