Skip to main content
Glama

azeth_discover_services

Discover trusted participants on the registry by filtering capabilities, entity types, and minimum reputation scores.

Instructions

Find services, agents, and infrastructure on the trust registry by capability, entity type, and reputation.

Use this when: You need to find a participant that offers a specific capability (e.g., "swap", "price-feed"), or you want to browse available services filtered by type and minimum reputation score.

Returns: Array of registry entries with token ID, owner, entity type, name, capabilities, endpoint, and status.

Note: This queries the Azeth server API. Set AZETH_SERVER_URL env var if the server is not at the default location. Results are ranked by reputation (highest first) by default; pass minReputation to also filter out providers below a threshold. Each result carries a usableEndpoint flag (false for blank/placeholder/ephemeral-tunnel endpoints). No private key is required for read-only discovery.

Example: { "capability": "price-feed" } or { "entityType": "service", "minReputation": 50, "limit": 5 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainNoTarget chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet").
capabilityNoFilter by capability (e.g., "swap", "price-feed", "translation").
entityTypeNoFilter by participant type.
minReputationNoMinimum reputation score (0-100). Higher means more trusted.
limitNoMaximum number of results. Defaults to 10.
offsetNoNumber of results to skip for pagination. Defaults to 0.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses critical behaviors: queries Azeth server API, environment variable configuration, default ranking by reputation, usableEndpoint flag, and that no private key is required. Minor omission: no mention of caching or rate limits, but acceptable for a read-only tool.

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

Conciseness4/5

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

The description is well-structured with front-loaded purpose, clear sections, and examples. It is 8 sentences, efficient but not overly terse. Minor redundancy: example at end repeats schema.

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

Completeness5/5

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

Despite lacking an output schema, the description fully explains the return format: 'Array of registry entries with token ID, owner, entity type, name, capabilities, endpoint, and status' plus 'usableEndpoint flag'. Combined with the rich input schema (6 params all described), the tool is completely contextualized.

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%, so baseline is 3. The description adds usage context (examples, ranking behavior) but does not significantly extend beyond schema details. The offset parameter is not explained in the description.

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 clearly states 'Find services, agents, and infrastructure on the trust registry' with specific verbs and resources. It distinguishes from siblings like 'azeth_discover_agent_capabilities' and 'azeth_get_registry_entry' by focusing on broad discovery with filtering.

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

Usage Guidelines4/5

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

The description provides explicit use cases: 'Use this when: You need to find a participant that offers a specific capability... or you want to browse available services filtered by type and minimum reputation score.' While it doesn't state when not to use, it gives sufficient context for appropriate tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/azeth-protocol/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server