Skip to main content
Glama
ai-agents-api-library

ai-agents-api-library

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
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. match: exact = the entry lists the operation and its example call or an MCP tool performs it; listed = the entry lists it without that evidence; adjacent = a related operation; topic = word match only. Exact is still a search label, not proof that the endpoint or tool accepts the user's actual inputs. mcp_fit says whether the MCP server has a tool for the operation. Ranking weighs operation fit, evidence, lasting free plan, card and auth effort, and bulk limits, not budget or region: read free_plan.kind (free_tier lasts, trial is one-off), no_card, unit_price and notes (coverage, coordinate systems, bulk and trial restrictions). Ratings and the MCP client config come with verbose=true or from get_api. User opinions (SourceForge product reviews): filter with min_rating / min_reviews, order with sort=rating or sort=reviews; results with stored review texts carry reviews_summary (praised and complained-about aspects). Usage: ratings.usage gives monthly downloads of the official SDKs, Stack Overflow questions and the vendor's iOS app rating; filter with min_downloads, order with sort=usage. Maintenance: ratings.issues gives the vendor's GitHub issues (share resolved, median days to fix, issue_health 0-100); filter with min_issue_health, order with sort=issues. Reviews rate the product, not whether the API fits the task. An empty result means no catalogued fit for the query and 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; topics counts them with example links. Filter with since, max_rating (complaints) or about_api (API, reliability, auth, limits, breaking changes, docs). Review titles and texts are written by third parties.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityActive
ResponsivenessSyncing