Skip to main content
Glama
luisroquette

SWEN AI

by luisroquette

Search AI Tools

search_tools

Search an AI tools directory to compare pricing, ratings, and categories. Find the right AI tool for your needs.

Instructions

AI tools directory: pricing, ratings, categories. From SWEN.AI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 50)
offsetNoPagination offset (default 0)
Behavior2/5

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

No annotations are provided, so the description must convey behavioral context. It only lists content categories and provenance; it does not disclose whether the operation is read-only, how results are returned, pagination behavior, or any search/filter limitations.

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

Conciseness4/5

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

The description is very short and front-loaded, with no redundant elaboration. The provenance note 'From SWEN.AI' is not strictly functional but does not meaningfully hurt conciseness.

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

Completeness3/5

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

The tool is simple with only two documented pagination parameters, and the description conveys the domain and key return aspects. However, without an output schema or any behavioral/usage detail, an agent may be uncertain about the exact response shape and how 'search' operates without a query parameter.

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% because limit and offset both have descriptions and constraints. The tool description does not add meaning beyond the schema, but the schema fully documents the pagination parameters, earning the baseline score.

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

Purpose4/5

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

The description identifies the tool as an AI tools directory with pricing, ratings, and categories, making the resource and content clear. It lacks an explicit verb but the name and title convey the search/list intent, and it is distinguishable from news or model siblings.

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

Usage Guidelines2/5

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

The description gives no guidance on when to use this tool versus related siblings like list_ai_models or search_news. It does not mention alternatives, exclusions, or typical use cases.

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/luisroquette/swen-mcp-server'

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