Skip to main content
Glama

Search endpoints

search_endpoints
Read-onlyIdempotent

Search the Octio catalog of pay-per-call APIs for trading agents. Returns up to 50 endpoints with path, name, description, price per call in CREDIT, free calls, health, and the last 7 days' success rate and p95 latency. It includes candles, technical indicators (RSI, EMA, SMA, MACD, Bollinger bands, ATR, stochastic), market snapshots, a screener and order book liquidity for crypto, US stocks, indexes and commodities (query "rsi", "candles", "scan", "liquidity"); SEC Form 4 insider trades for US stocks (query "insider"); Robinhood Chain stock-token premiums against the reference price (query "premium"); transaction simulation and explanation and address checks on Robinhood Chain and Base (query "simulate", "address"); web page reading, link metadata, PDF text, prompt-injection scans and URL safety checks (query "web", "pdf", "injection"). With no query it lists everything. Free, and works without an API key.

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": "search_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoWords to match in the endpoint path, name, description or provider, such as "rsi", "insider" or "simulate"; leave it out to list everything
categoryNoOnly endpoints in this category
max_priceNoOnly endpoints priced at or below this many CREDIT per call

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a hard result cap of 50 endpoints, the exact fields returned, and the fact that it is free and works without an API key — all of which affect whether and how an agent calls it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and result shape are front-loaded in the first two sentences, and the long category tour is dense with query hints that earn their space. The enumeration is on the edge of being a catalog dump, but every clause maps to a distinct content area an agent might query.

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?

For a three-optional-parameter search tool with an output schema and read-only annotations, the definition covers scope, result cap, returned fields, query strategy, no-query fallback, cost and auth requirements. 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 description coverage is 100%, so all three parameters are already documented in the schema, which sets the baseline at 3. The description restates the query semantics and the no-query case and implicitly hints at what subject matter the catalog covers, but adds no syntax or format detail beyond the schema for query, category or max_price.

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 opens with a specific verb and resource ('Search the Octio catalog of pay-per-call APIs for trading agents') and enumerates exactly what categories of endpoints live in that catalog. An agent can immediately distinguish this catalog-search tool from get_endpoint (fetch one) or call_endpoint (invoke one) without opening any schema.

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?

It gives concrete usage context by mapping example query strings to content areas ('query "rsi", "candles"...', '"insider"', '"simulate"', '"web"'), and it states the fallback behavior of omitting the query. It does not explicitly say when to prefer a sibling like get_endpoint over this search, so it stops short of full alternatives guidance.

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