ai-agents-api-library
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_categoriesA | List all categories in the catalog with the number of services in each. |
| search_apisA | Find a third-party API or MCP server for a capability you lack, among 300+ catalog entries with a last-checked date: auth method, free plan, MCP endpoint, docs. Use it after checking your built-in and connected tools and your own model; skip it if they already do the job (e.g. translating or drawing a diagram yourself). Also use it when your own direct attempt failed (403, rate limit, unsupported format). Each result has |
| get_apiA | Full entry for one service: docs, auth scheme and how the credential is sent, base URL, operations, MCP endpoint or repository (check which: a repository must be installed, a docs-only server does not call the API), free plan vs trial, rate limits, data policy, notes, last-checked dates, link check, and separate signals: uptime (our availability probes of base URL and MCP endpoint), mcp_repo (archived, last push), mcp_registry (installs) and product_reviews (rating, count, date range), each with its fetch date. Values come with the vendor page they were read from; confirm pricing and terms there before real use. |
| get_reviewsA | Public user reviews of one service (up to 100, from SourceForge): rating, title, pros, cons, overall, reviewer role, company size, date and link to the original. Reviewer names are not included. Optional: use when real-world quality matters to the choice, e.g. to break a tie; reviews do not show whether the API fits the task. Each review has aspect tags; |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a clear, distinct purpose: listing categories, searching for APIs, retrieving full API details, and fetching user reviews. There is no overlap or ambiguity in their roles.
All tool names follow a consistent verb_noun pattern in snake_case: list_categories, get_reviews, search_apis, get_api. The naming is predictable and readable.
Four tools is a well-scoped set for an API catalog lookup server: browse by category, search, get details, and get reviews. Each tool has a clear place in the workflow.
The domain is read-only API discovery and evaluation, and the surface fully covers it: categorization, search, detailed metadata, and third-party reviews. No obvious gaps for the stated purpose.