Skip to main content
Glama

ecosystem_search

Query an archive of ecosystem repository profiles to find relevant repos by keyword, topic, stars, language, and more. Filter and sort results to discover tools for agent frameworks, MCP servers, and other AI system components.

Instructions

Query ecosystem_repo_profiles archive (Stage E enhanced).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNostars (default) / recency (pushed_at desc) / relevance (relevance_score desc).stars
tagsNoTag name list, semantic capability filter.
limitNoMax results (default 30, server max 200).
topicNoTopic keyword filter (JSON field LIKE match).
offsetNoPagination offset.
keywordNoKeyword match (name / description / summary / repo_full_name / description_excerpt).
categoryNoCategory filter (agent-framework / mcp-server / memory-system / skill-system / tooling).
languageNoProgramming language filter (e.g. Python / TypeScript).
max_starsNoMaximum star count (0 = no limit).
min_starsNoMinimum star count.
project_idNo
is_archivedNoTrue/False to filter archived repos; None = no filter.
facet_countsNoWhen True, response includes facet_counts (category/language/archived).
pushed_afterNoISO datetime — only repos with pushed_at >= this. Empty = no filter.
tag_match_modeNo"all" (AND) / "any" (OR). Default all.all
needs_deep_reviewNoTrue/False filter; None = no filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior1/5

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

No annotations exist, and the description does not disclose any behavioral traits (e.g., read-only, side effects, rate limits, permissions). The description fails to carry the burden in the absence of annotations.

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

Conciseness2/5

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

The description is extremely short (one sentence), but this brevity comes at the cost of clarity and completeness. It sacrifices essential information for conciseness.

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

Completeness1/5

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

Given the tool complexity (16 parameters, output schema, many siblings), the description is completely inadequate. It does not explain the archive, the 'Stage E' concept, or how this search differs from others.

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

Parameters2/5

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

Schema coverage is 94%, so baseline is 3, but the description adds zero parameter meaning. It does not elaborate on parameters beyond what the schema already provides. Not harmful, but no added value.

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

Purpose2/5

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

The description states 'Query ecosystem_repo_profiles archive' which is a verb+resource, but is vague and does not differentiate from many sibling search tools like ecosystem_search_by_capability or ecosystem_repo_get. 'Stage E enhanced' adds no clarity.

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

Usage Guidelines1/5

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

No usage guidelines provided. The description gives no indication of when to use this tool versus alternatives, nor any prerequisites or context.

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/CronusL-1141/AI-company'

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