Teardrop

Discover Agents

discover_agents

Read-only

Find opt-in remote A2A agents, published tool capabilities, endpoints, and public reputation status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`q`	No	Optional search across agent name, organization slug, or published tool name
`limit`	No	Maximum number of agents to return

Output Schema

TableJSON Schema

Name	Required	Description
`count`	Yes
`agents`	Yes
`generated_at`	Yes
`registration_endpoint`	No	Endpoint where an organization can publish its own A2A endpoint.
`registration_benefits_url`	No	Machine-readable registration benefits, requirements, and non-guarantees.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedSep 4, 2026

addedOutput schema / properties / registration_benefits_url

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Machine-readable registration benefits, requirements, and non-guarantees.",
+  "title": "Registration Benefits Url"
+}

addedOutput schema / properties / registration_endpoint

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Endpoint where an organization can publish its own A2A endpoint.",
+  "title": "Registration Endpoint"
+}

Changed3 schema fields changedSep 4, 2026

changedInput schema / properties / q / description

Previous value: -"Optional search across agent name and organization slug"New value: +"Optional search across agent name, organization slug, or published tool name"

addedOutput schema / $defs / DiscoveredAgent / properties / registered_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "UTC timestamp when the organization first registered its A2A endpoint",
+  "title": "Registered At"
+}

addedOutput schema / $defs / DiscoveredAgent / properties / tool_names

Added value: +{
+  "description": "Names of up to 20 active published tools exposed by the agent organization",
+  "items": {
+    "type": "string"
+  },
+  "title": "Tool Names",
+  "type": "array"
+}

AddedAug 31, 2026

TDQS

A3.6/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already carry the readOnlyHint=true safety profile. The description adds useful scoping context — only opt-in, publicly-registered agents with published reputation are returned — which is genuine behavioral information. However, it does not disclose search semantics, matching behavior, or the nature of the registry being queried.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that leads with the verb 'Find' and packs in the resource plus three result attributes with zero filler. Every word earns its place, and the description is appropriately sized for the tool's simplicity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a full output schema, completely documented parameters, and a readOnlyHint annotation, so the description need not explain return values or safety. The essential call context is present. The only gap is usage differentiation from delegate_to_agent, which is minor for a simple discovery tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%: both q (search across agent name, organization slug, or published tool name) and limit (max returns, bounds, default) are fully documented. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Find') with a precise resource ('opt-in remote A2A agents') and enumerates what results include (published tool capabilities, endpoints, public reputation status). This clearly distinguishes the tool from its sibling delegate_to_agent, which is about interacting with an agent rather than discovering one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states what the tool finds but gives no conditions for when to use it over alternatives. It never references delegate_to_agent or any other sibling, and offers no exclusion criteria or prerequisites — the agent is left to infer the appropriate scenario.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Teardrop tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0

Disambiguation3/5

Most tools target distinct data sources, but several near-duplicates exist: get_token_approvals/get_wallet_approvals, get_defi_positions/get_wallet_positions, and get_wallet_portfolio/get_eth_balance. The descriptions do cross-reference and clarify the differences, so an agent can disambiguate with effort, but names alone are not enough.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and nearly all names use lowercase snake_case with verb-first conventions. A few tools like calculate, record_predictions, http_fetch, and web_search break the get_ pattern, but the overall style remains predictable.

Tool Count2/5

34 tools is excessive for a single server, even for a broad DeFi/onchain analytics domain. The count is inflated by generic utilities such as calculate, count_text_stats, web_search, and http_fetch, plus multiple overlapping data-retrieval endpoints, making the surface hard to scan.

Completeness4/5

The set covers an unusually wide range of domain operations: prices, balances, portfolio/positions, approvals, yields, TVL, DEX quotes/volume, transactions, blocks, gas, ENS, contract reads, and risk assessments. It is view-only by design, so missing write/transaction tools is acceptable; minor gaps like address-based token pricing or transaction simulation are workaround-able.

Resources

Need Help?