Skip to main content
Glama
mmadfox

swag2mcp

by mmadfox
OverviewSchemaRelated ServersScoreDiscussions
Go
Hybrid

search

Read-onlyIdempotent

Find API endpoints across all specifications using natural language or structured queries. Filter by HTTP method, tag, or path to target the exact endpoint you need.

Instructions

search

The ONLY tool for finding endpoints when you don't have the endpoint ID.

Searches endpoints across all specifications using full-text and structured queries.

When to use

Use this tool when:

  • The user asks to find a method/endpoint by description, name, path, tag, or functionality

  • The user describes functionality without knowing specific paths or tags

  • You need to find relevant endpoints based on natural language descriptions

  • You want to filter by HTTP method (method:GET), tag (tag:auth), or path (path:user)

DO NOT

  • ❌ Do NOT manually traverse spec → collection → tag → endpoint to find something. Use search.

  • ❌ Do NOT guess endpoint IDs. Use search.

  • ❌ Do NOT use endpoint_by_tag / endpoint_by_collection / endpoint_by_spec for discovery — those are for navigation after you already know what you're looking for.

  • ❌ Do NOT skip search and try to brute-force your way through collections. One search call replaces dozens of manual navigation steps.

User Intent → Search Query Examples

User says

What to search

"Find the create user endpoint"

+method:POST +summary:create +summary:user

"Show all GET endpoints"

method:GET

"What relates to orders?"

order

"Find endpoint by path /api/v1/users"

path:"/api/v1/users"

"How do I delete a pet?"

+method:DELETE +summary:pet

"Show all auth endpoints"

tag:auth

"Find something about inventory"

inventory

"Give me all POST requests in the store section"

+method:POST +tag:store

Parameters

  • query (required): Natural language or structured search query. Supports field filters (method:POST, tag:pet, path:/api/v1/*), boolean operators (+ must, - exclude), fuzzy (term~), wildcards (*, ?), and phrases ("exact phrase"). path: filters match the full path prefix — e.g. path:/api/v3/* returns only endpoints whose path starts with /api/v3/; path:/api/v3/users matches that exact path. Queries containing / use AND between tokens — e.g. /v1/seasonal matches only endpoints with both v1 AND seasonal, not all /v1/* endpoints.

  • limit (required): Maximum number of results to return (min: 1, max: 50)

Returns

A list of endpoints matching the query with their IDs, methods, paths, and summaries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitYesrequired,Maximum number of results to return
queryYesrequired,Search query. Supports field filters (method:GET tag:pets path:/v1/...). Queries containing '/' use AND between tokens for precise path matching.

Tool Definition Quality

A5/5.0
Behavior5/5

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

Even with readOnlyHint and idempotentHint annotations, the description adds rich behavioral context: query syntax (field filters, boolean operators, fuzzy, wildcards, phrases), path prefix matching nuance (e.g., 'path:/api/v3/*' matches only prefixes), the AND behavior for queries with '/', and the return format (list with IDs, methods, paths, summaries).

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?

The description is long but impeccably structured with headers, bullet lists, a table of examples, and clear sections. Every sentence contributes to understanding the tool, and the formatting makes it scannable without redundancy.

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?

For a simple 2-parameter tool with no output schema, the description fully covers what the tool does, how to use it, what parameters mean, and what it returns (list of endpoints with IDs, methods, paths, summaries). No critical information is missing.

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

Parameters5/5

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

Although schema coverage is 100%, the description vastly expands parameter semantics. It details query syntax (method:, tag:, path:, boolean +/-, fuzzy ~, wildcards *, phrases), provides explicit examples for each filter, and adds min/max constraints for the limit parameter not present in the schema.

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 opens with a definitive statement: 'The ONLY tool for finding endpoints when you don't have the endpoint ID.' It clearly specifies the action (searches endpoints) and resource (across all specifications), and distinguishes itself from sibling tools like endpoint_by_tag and endpoint_by_collection by stating those are for navigation after you already know what you're looking for.

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

Usage Guidelines5/5

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

The 'When to use' section provides explicit triggers, and the 'DO NOT' section lists alternatives and warns against manual traversal. The user intent-to-search-query examples further clarify when and how to apply the tool in practical scenarios.

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/mmadfox/swag2mcp'

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