Skip to main content
Glama
CronusL-1141

AI Team OS

by CronusL-1141
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ecosystem_search_by_capability

Search ecosystem repositories by capability tags using reverse lookup. Returns full profile rows and matched tags for each repo.

Instructions

Search ecosystem repos by capability tags (reverse lookup from tag → repo).

Runs the same query as ecosystem_search(tags=..., tag_match_mode=...) but returns full profile rows (no compact projection) and echoes matched_tags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNostars (default) / recency (recently pushed first) / relevance (relevance_score desc).stars
tagsNoTag name list (e.g. ["memory_system", "vector_db"]).
limitNoMax rows per page (default 30, server max 200).
offsetNoRows to skip — pagination cursor for the next page.
max_starsNoPopularity ceiling; 0 (default) = no limit. Set it to exclude the famous head and surface lesser-known projects.
min_starsNoPopularity floor; 0 (default) keeps niche repos in.
match_modeNo"all" (AND, default) — repo must carry every tag; "any" (OR) — repo carries at least one, use it to widen a search that returned too few hits.all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.11.2
    • addedInput schema / properties / limit / description
      Added value: +"Max rows per page (default 30, server max 200)."
    • changedInput schema / properties / match_mode / description
      Previous value: -"\"all\" (AND, default) / \"any\" (OR)."New value: +"\"all\" (AND, default) — repo must carry every tag;\n\"any\" (OR) — repo carries at least one, use it to widen a\nsearch that returned too few hits."
    • addedInput schema / properties / max_stars / description
      Added value: +"Popularity ceiling; 0 (default) = no limit. Set it to\nexclude the famous head and surface lesser-known projects."
    • addedInput schema / properties / min_stars / description
      Added value: +"Popularity floor; 0 (default) keeps niche repos in."
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip — pagination cursor for the next page."
    • changedInput schema / properties / sort / description
      Previous value: -"stars / recency / relevance."New value: +"stars (default) / recency (recently pushed first) /\nrelevance (relevance_score desc)."
  2. First observedv1.9.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure. It adds useful context about query equivalence and output shape (full rows, matched_tags), but does not state read-only safety, side effects, auth needs, rate limits, or pagination behavior. Since an output schema exists, return details are less critical, but the gap in safety/operational traits keeps this at a 3.

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?

Two sentences, front-loaded with the core purpose and immediately followed by the distinction from the sibling tool. No wasted words.

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?

An output schema exists, so return values needn't be explained, and the description covers the essential purpose and sibling differentiation. It does not go into when to prefer this over other ecosystem-related search tools or edge-case behavior, but it is largely complete for a search endpoint with rich schema coverage.

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 the schema already documents all 7 parameters thoroughly. The description references tags and tag_match_mode as parameters of ecosystem_search, but adds no meaning beyond what the schema provides for this tool's own parameters. Baseline 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 states a specific verb (Search), resource (ecosystem repos), and scope (by capability tags, reverse lookup from tag → repo). It explicitly differentiates from the sibling ecosystem_search by noting it runs the same query but returns full profile rows and echoes matched_tags, so an agent can tell them apart without opening schemas.

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?

It names ecosystem_search as the alternative and clarifies the key difference (full profile rows vs compact projection, plus echoed matched_tags). This implies when to choose this tool, but it does not explicitly state when-not to use it or contrast with other ecosystem search siblings like ecosystem_summary_by_tag or ecosystem_tag_list.

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

Deploy Server

Other Tools