Skip to main content
Glama

Search the API directory

discover_monitored_apis
Read-onlyIdempotent

Searches the 21,160 APIs and MCP servers indexed by AgentSLA by keyword and/or category. Use it first to find candidate services; then get_api_details for one listing, or check_endpoint to test a URL live. Free, read-only, served from the index (no live probing). Returns totalIndexed, matchedCount and up to limit listings, each with id, service_name, endpoint_url, category, link_type ("api" = callable endpoint, "listing-page" = a directory page about the service, "spec-file" = an API description file) and current_sla_score (share of recent probes that answered, null if never probed). Callable APIs come first. When a category matches nothing, availableCategories lists the valid ones.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "discover_monitored_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum listings to return.
searchNoKeywords matched against service name and URL, e.g. "weather", "stripe", "solana rpc". Omit to browse a category.
categoryNoCategory slug: mcp-connectors, ai-models, data-retrieval, autonomous-agents, cloud, developer_tools, web3-rpc, image-generation, security, financial, marketing, analytics, ecommerce, iot, payment, defi-data. Display names such as "Web3 RPC" or "LLM Inference & AI Models" also work. Omit for all categories.
callableOnlyNotrue returns only callable endpoints (link_type "api"), skipping directory pages and spec files.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / callableOnly / default
      Added value: +false
    • changedInput schema / properties / callableOnly / description
      Previous value: -"Only return callable APIs (link_type \"api\"). Default false."New value: +"true returns only callable endpoints (link_type \"api\"), skipping directory pages and spec files."
    • changedInput schema / properties / category / description
      Previous value: -"Optional category: mcp-connectors, ai-models, data-retrieval, autonomous-agents, cloud, developer_tools, web3-rpc, image-generation, security, financial, marketing, analytics, ecommerce, iot, payment, defi-data. Display names such as \"Web3 RPC\" or \"LLM Inference & AI Models\" are accepted too."New value: +"Category slug: mcp-connectors, ai-models, data-retrieval, autonomous-agents, cloud, developer_tools, web3-rpc, image-generation, security, financial, marketing, analytics, ecommerce, iot, payment, defi-data. Display names such as \"Web3 RPC\" or \"LLM Inference & AI Models\" also work. Omit for all categories."
    • addedInput schema / properties / limit / default
      Added value: +25
    • changedInput schema / properties / limit / description
      Previous value: -"Max results to return (default 25, max 200)"New value: +"Maximum listings to return."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / search / description
      Previous value: -"Optional keyword search across service name and URL (e.g. solana, stripe, github, weather)"New value: +"Keywords matched against service name and URL, e.g. \"weather\", \"stripe\", \"solana rpc\". Omit to browse a category."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, not open-world), and the description adds genuinely new context: it is free, served from a static index rather than live probing, callable APIs sort first, and unmatched categories return availableCategories. These are operational traits the agent cannot infer from the annotations.

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?

Front-loaded with purpose and routing, then return shape, then ordering and fallback behavior. The return-field enumeration is longer but pays for itself because no output schema exists; no sentence is filler.

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?

There is no output schema, so the description carries return values — and it does, naming totalIndexed, matchedCount, and each listing field including link_type semantics and null SLA scores. Combined with free/read-only behavior and category fallback, nothing needed to call it correctly is missing.

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 coverage is 100%, so the schema already explains all four parameters, including that `search` omits to browse and `callableOnly` filters to link_type "api". The description mostly echoes those meanings rather than adding syntax or edge-case guidance, so baseline 3 is appropriate.

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?

States a specific verb and resource ("Searches the 21,160 APIs and MCP servers indexed by AgentSLA by keyword and/or category") and immediately distinguishes itself from siblings get_api_details (one listing) and check_endpoint (live probing). An agent can tell exactly what this tool does without opening the schema.

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?

Gives explicit ordering guidance ("Use it first to find candidate services") plus named alternatives and the condition selecting each: get_api_details for one listing, check_endpoint to test a URL live. The "no live probing" note also clarifies what this tool will not do.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources