Skip to main content
Glama
Sign In

API Status Check

by io.github.shibley
OverviewDiscussionsAdmin

Search monitored APIs

search_apis

Find monitored APIs by name, slug, category or description. Use this to resolve a product name the user mentioned into the slug the other tools take.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_apis"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 25).
queryYesFree-text query, e.g. "openai" or "payments".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly implies a non-destructive search operation, but it does not disclose the return format, whether results are exact or fuzzy matches, or pagination behavior. This leaves some behavioral ambiguity.

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?

The description is two sentences, front-loaded with the core action and resource, and the second sentence provides practical context without waste. It is compact and informative.

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

Completeness4/5

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

For a simple search tool with 100% schema coverage and no output schema, the description is sufficient: it states what is searched, the resolution purpose, and the limit parameter is already documented. Sibling tools provide additional context. The main gap is a lack of detail about the result structure, but that is not critical for selection.

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%: both 'query' and 'limit' are described with examples, defaults, and constraints. The description adds that query can match name/slug/category/description, which reinforces the schema but doesn't add new parameter semantics. This is the baseline 3.

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?

The description clearly states the action ('Find') and the resource ('monitored APIs'), and enumerates the searchable fields (name, slug, category, description). It also distinguishes the tool from sibling list tools by explaining that it resolves a product name into the slug used by other tools.

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

Usage Guidelines4/5

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

The description explicitly says 'Use this to resolve a product name the user mentioned into the slug the other tools take,' which gives a concrete use case and implies that alternatives require the slug. However, it doesn't explicitly name sibling tools or state when not to use it, so it stops short of a 5.

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

All API Status Check toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources