discover_capabilities

app.agentnexus/agent-nexus · Verify this server

Use this when you have a goal in plain language and no idea which interface serves it (e.g. 'send a transactional email', 'query Postgres'). Returns {need, coverage, count, uncovered, note, matches[]}; each match carries slug, name, category, endpoint, auth mode and parameters, input/output formats, rate limit, pricing and a 0-100 reliability score — everything needed to call it. Never empty and never an error on a valid need: when nothing matches, coverage='none', uncovered=true and matches[] holds reliable starting points instead. Invalid input is rejected with a validation message; the registry being unreachable is returned as an error result. Parameter guidance: write 'need' as a task, not a keyword ('send a transactional email', not 'email'); leave 'category' unset unless you specifically require one layer, since the best interface for a need is often in another; raise 'limit' when you intend to compare candidates; and use 'min_reliability' (e.g. 60) only for production calls, as it can empty an otherwise useful result set. For a known keyword, slug, vendor or category, use search_registry instead.