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 | Search 300+ catalog entries of third-party APIs and MCP servers (each with a last-checked date) by operation or keywords, with optional category and quality filters. |
| get_apiB | Full entry for one service: docs, auth scheme and how the credential is sent, base URL, operations, MCP endpoint or repository (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), product_reviews (rating, count, date range), sdk_downloads (official npm/PyPI SDKs per month), stackoverflow (question count), app_store (the vendor's iOS app) and github_issues (open vs resolved issues, median days to fix and issue_health 0-100 of the SDK, MCP and spec repos), each with its fetch date. Values carry the vendor page they were read from and a check date. |
| 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. 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 targets a distinct step: browsing categories, searching the catalog, fetching a single entry, and pulling third-party reviews. The only soft overlap is that get_api already surfaces a product_reviews signal and search results can carry reviews_summary, so an agent might occasionally reach for get_reviews when get_api would do; the descriptions do clarify the split.
All four names follow a strict verb_noun snake_case pattern (list_categories, search_apis, get_api, get_reviews). Singular/plural resource nouns are used sensibly (one api vs. many apis) rather than inconsistently.
Four tools is a tight, well-scoped surface for a read-only API catalog: browse, search, detail, and reviews. No tool is redundant and none feels like padding.
The read-only lifecycle of a catalog (discover by category, search with filters, inspect one entry in full, read external reviews) is covered, and search's category filter substitutes for a dedicated list-by-category tool. Minor gaps remain: no way to compare multiple entries side by side or enumerate the full catalog without a query, but agents can work around these via search.