Skip to main content
Glama

OpenAny overview

openany_overview
Read-onlyIdempotent

Return live catalog counts from the current snapshot. No arguments. Does not call the paid gateway. api_count and model_count are totals. apis_by_provider and apis_by_category group data APIs. models_by_modality groups model ids by primary modality: chat/reasoning, image, video, and audio. example_questions lists ready-to-ask questions in en and zh for categories the snapshot can still serve. On a first or vague message, present that intro and do not search yet. Then search_apis, get_api, and run_api only after the user confirms the live price.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing a cost boundary (no paid gateway call), a data-freshness caveat (current snapshot), and the gating rule that downstream tools must wait for price confirmation.

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?

Purpose and the no-cost/no-args constraints are front-loaded, then the return fields are enumerated compactly. The middle run of field explanations (api_count, apis_by_provider, models_by_modality, example_questions) is dense but each line carries distinct semantics, so little is wasted apart from a slightly list-like rhythm.

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 must carry return semantics itself, and it does: it defines totals versus grouped breakdowns, explains the modality grouping values, and notes that example_questions come in en and zh. Combined with the workflow gating, an agent has everything needed to call and present this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the completely empty schema is already fully documented and the description's "No arguments" is merely confirmatory. Baseline for a 0-parameter tool applies.

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?

Opens with a specific verb+resource+scope ("Return live catalog counts from the current snapshot") and immediately bounds it ("Does not call the paid gateway", "No arguments"). That distinguishes it cleanly from the sibling tools search_apis, get_api, and run_api, which operate on individual APIs rather than snapshot aggregates.

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 sequencing: on a first or vague message, present the intro and do not search yet; call search_apis/get_api/run_api only after the user confirms the live price. Both the when-to-use and the when-not-to-use are stated, and the alternatives are named with the condition that selects them.

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.