Loading ToolBench

Reading the current corpus…

agent-discovery-nextjs MCP server · F · ToolBench

agent-discovery-nextjs

github.com/hashgraph-online/agent-discovery-nextjs

A Next.js web application that helps users find AI agents across multiple registries including NANDA, MCP, A2A, Virtuals, and OpenRouter using the Registry Broker API.

2026-07-28+STREAMABLE_HTTP2 tools

21/100

Definition Quality20

Protocol Readiness0

Supportability35

Spec posture

Inferred effective spec 2026-07-28+·current baseline 2026-07-28

Static source inference · medium confidence · evidence: Streamable HTTP

Current-spec patterns detected

Summary

This is NOT an MCP server. It is a Next.js chat application that uses the Vercel AI SDK to call external tools via @hol-org/ai-sdk-registry-broker. The tools are created dynamically by a third-party library, not defined in this codebase. Tool definitions are inferred from function names only; no explicit schemas, parameter descriptions, or output documentation are visible in the source. Per the hard rules, inferred tools cap at 50; combined with missing schemas and descriptions, the overall score is critically low.

Tools (2)

registry_broker_resolveread only25/100

Get comprehensive information about a specific agent using its UAID

registry_broker_searchread only25/100

Search for relevant agents across multiple registries

Issues (5)

CRITICALtool ↗

No input schemas visible. Tools are created by external library; no parameter types, constraints, or descriptions are defined in this codebase.

registry_broker_searchregistry_broker_resolve

CRITICALtool ↗

Tool definitions are inferred, not explicitly registered. Cannot verify actual parameter names, types, or output schemas from source code.

registry_broker_searchregistry_broker_resolve

HIGHtool-description ↗

Descriptions are generic and under 50 characters. 'Search for relevant agents across multiple registries' lacks context on when to use this vs resolve, what parameters it accepts, or what the output structure is.

registry_broker_searchregistry_broker_resolve

HIGHrecovery-guide ↗

No error handling guidance. If a search returns no results or a UAID is invalid, the LLM has no recovery path documented.

registry_broker_searchregistry_broker_resolve

Recommendations

If this is intended to be an MCP server, rewrite it as a proper MCP server using the Node.js SDK (mcp package). Implement tool registration with explicit schemas, descriptions, and error handling.
If this is a client application, document the actual tool schemas from @hol-org/ai-sdk-registry-broker in a separate schema file or README so users understand what parameters and outputs are available.
Add parameter descriptions for each tool: what does 'search' accept? (query string? filters? pagination?). What does 'resolve' expect? (UAID format? case-sensitive?)
Document output schemas: what fields does registry_broker_search return? (agent_id, name, description, protocol, url?). What does registry_broker_resolve return?
Add error handling examples: 'If no agents match the search, try broader keywords or filter by protocol. If UAID is invalid, use search first to find the correct UAID.'

Score history

Overall score trend

First recorded score · v2 rubric

21/100

Scored	Grade	Overall	Spec posture	Rubric
2026-09-23	F	21	2026-07-28+	v2