Skip to main content
Glama

search_collections

Read-only

Search Ansible Galaxy for collections by keyword to discover which collection provides modules for a specific platform or use case, returning non-deprecated collections ranked by download count.

Instructions

Search Ansible Galaxy for collections by keyword.

Returns non-deprecated collections ranked by download count. Use this to discover which collection provides modules for a specific platform or use case.

After finding a collection, use ensure_collection() to install it, then get_module_doc() or get_collection_manifest() to explore its modules.

Returns: {"query": str, "count": int, "collections": [{"namespace": str, "description": str, "tags": [str], "latest_version": str, "module_count": int, "download_count": int, "deprecated": bool, "signed": bool}, ...]} On failure returns {"error": str}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoOptional comma-separated Galaxy tags to filter (e.g., 'networking,cloud')
queryYesSearch keyword (e.g., 'netbox', 'cisco ios', 'vmware')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint=true. Description adds return format, non-deprecated filtering, and ranking by download count. No contradiction. Adds value beyond annotations.

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?

Three sentences plus return structure. Front-loaded with action. No redundant words.

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?

Complete for a search tool with output schema: covers purpose, usage, return format (including error), and workflow with siblings.

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 coverage is 100% with descriptions. Description does not add significant parameter details beyond schema. Baseline 3 appropriate.

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?

Clearly states verb 'Search' and resource 'Ansible Galaxy collections'. Distinguishes from siblings like ensure_collection and get_module_doc. Specifies it returns non-deprecated collections ranked by download count.

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?

Explicitly says to use for discovering which collection provides modules for a platform/use case. Provides follow-up actions (ensure_collection, get_module_doc). Lacks explicit when-not-to-use but strong positive guidance.

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/leogallego/ansible-know-mcp'

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