Skip to main content
Glama
tadas-github

a2asearch-mcp

by tadas-github

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_agentsA

Search the A2ASearch directory for AI agents, MCP servers, CLI tools and agent skills. Returns name, description, type, stars, GitHub URL and capabilities for each result.

get_agentB

Get full details for a specific agent by its slug (name as kebab-case). Returns description, README, capabilities, stars, forks, languages and more.

list_agentsB

List agents from A2ASearch, optionally filtered by type. Use this to browse top agents by category.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_agent retrieves detailed information for a specific agent, list_agents provides a filtered browse of agents by category, and search_agents performs a broader search across the directory. There is no overlap in functionality, making tool selection unambiguous.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (get_agent, list_agents, search_agents) with clear, descriptive verbs and pluralization where appropriate. This uniformity aids in predictability and readability.

Tool Count4/5

With 3 tools, the count is slightly low but reasonable for the server's purpose of searching and browsing agents. It covers core operations (get, list, search), though additional tools like update or delete might be expected if the domain included management capabilities.

Completeness4/5

The tool set provides comprehensive coverage for searching and browsing agents, with no obvious gaps in this domain. However, it lacks CRUD operations (e.g., create, update, delete), which might be expected if the server also supported agent management, but based on the descriptions, the focus appears to be on discovery.

Maintenance

ActivityInactive
ResponsivenessUnresponsive