agentView

Search Public APIs

search_public_apis

Read-onlyIdempotent

Searches a curated catalog of 600+ free public APIs (no key, HTTPS) for embedding live data in display HTML via fetch(): weather, news, finance, sports, images, food and 40+ more categories. Use when generating HTML that needs live internet data. Set list_categories=true to get the category menu with counts instead of search results. Returns docs links, CORS status and fetch() hints. No authentication required.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum results, 1-20. Default 10.
`query`	No	Free-text search, e.g. 'weather forecast', 'bitcoin price', 'jokes'.
`category`	No	Category ID filter, e.g. 'weather', 'finance', 'news'. Omit for all.
`cors_only`	No	true returns only APIs with confirmed browser CORS support. Default false.
`list_categories`	No	true returns all categories with API counts instead of search results.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No
`query`	No
`results`	No
`category`	No
`corsOnly`	No
`categories`	No
`totalCatalogApis`	No

TDQS

A4.6/5.0

Behavior5/5

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

Discloses no authentication required, returns docs links, CORS status, and fetch() hints. Annotations already declare readOnlyHint and idempotentHint, and the description adds context about the curated catalog size and category count.

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?

Two sentences, well front-loaded with purpose and usage. Second sentence is slightly long but packs important details. No wasted words.

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?

Given 5 parameters and output schema present, the description covers key use cases, parameter behavior, and return details. No gaps identified.

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?

Schema coverage is 100%, so baseline 3. Description adds value by explaining list_categories behavior beyond schema (returns category menu with counts), and gives query examples like 'weather forecast'.

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?

Description clearly states it searches a curated catalog of free public APIs, specifying the use case for embedding live data in HTML via fetch(). It distinguishes from sibling tools like search or search_store_templates by focusing on public APIs with no auth required.

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?

Explicitly says 'Use when generating HTML that needs live internet data' and describes the list_categories option for category navigation. Does not mention alternatives, but context signals and sibling list provide differentiation.

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

All agentView tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0

Disambiguation4/5

Most tools map cleanly to distinct resource-action pairs (displays, organizations, assets, data slots, store templates, auth). A few clusters like the get_store_template_* family and the auth/session tools could still confuse an agent, but their descriptions are explicit enough to separate them.

Naming Consistency4/5

The dominant pattern is consistent verb_noun snake_case (list_*, get_*, create_*, delete_*, send_*, set_*, manage_*). Deviations like fetch, search, authenticate, logout, and pair_by_code are understandable but break the otherwise uniform naming scheme.

Tool Count1/5

With 57 tools this server far exceeds the 50+ threshold, creating an extreme tool-set size for an MCP server. Even though the underlying platform is feature-rich, the sheer number of tools heavily taxes context and selection.

Completeness4/5

The surface covers display, organization, asset, data slot, store template, auth, API key, and licensing lifecycles in impressive depth. Minor gaps exist, such as no delete operation for display categories and no reboot/power control for displays.

Resources

Need Help?