Skip to main content
Glama

PPN Hub — public APIs over MCP

by com.ppn-hub
OverviewDiscussionsAdmin

search_apis

Search across 519 endpoints in 60 APIs (amenomi, cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks). Returns matching endpoints with method, path, summary, parameters, and a ready-to-run example. Use this to discover available API endpoints before calling execute_api. Results carry a "coverage" field (e.g. ["JP"]) for region-limited APIs; use the "region" filter to narrow.

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by OpenAPI tag
limitNoMax results (default: 20)
queryYesSearch term (matches operationId, summary, description, path, API name, tags; synonyms expanded)
domainNoFilter by domain: amenomi, cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks
methodNoFilter by HTTP method
regionNoFilter by ISO 3166-1 alpha-2 region the API serves data for (e.g. "JP"). Returns region-specific + global APIs; excludes APIs limited to other regions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks"New value: +"Filter by domain: amenomi, cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks"
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"New value: +"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, space, stocks"
  3. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"New value: +"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanobase, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"
  4. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Filter by domain: cultural, earth, energy-calc, esg, green-path, harmonias, hydrogen, internal, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"New value: +"Filter by domain: cultural, earth, energy-calc, green-path, harmonias, hydrogen, internal, nanosnap, natura, platform, sakurahub, science, sim, social, space, stocks"
  5. Changed1 schema field changed
    • addedInput schema / properties / region
      Added value: +{
+  "description": "Filter by ISO 3166-1 alpha-2 region the API serves data for (e.g. \"JP\"). Returns region-specific + global APIs; excludes APIs limited to other regions.",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
  6. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the shape of results (method, path, summary, parameters, ready-to-run example) and the semantics of the "coverage" field for region-limited APIs. It does not mention auth requirements, rate limits, or whether results are cached/paginated, which keeps it below 5.

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?

Front-loaded with scope, then return shape, then routing, then region caveat – a logical order with no filler. The inline list of 17 domain names duplicates the domain parameter enum in the schema and is the one piece of avoidable bulk.

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?

There is no output schema, so the description must describe returns, and it does: matching endpoints plus a ready-to-run example, with the coverage field explained. Combined with the execute_api routing, an agent has what it needs to call this correctly; only operational details like limits or auth are absent.

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 six parameters are already documented in the schema, including the region filter's exact behavior. The description's mention of the region filter and coverage field largely restates schema content, so the baseline 3 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?

States a specific verb (search) and resource (API endpoints) and quantifies scope: 519 endpoints across 60 named APIs. It also names the sibling it feeds into (execute_api), so an agent can distinguish it from execute_api and environment_brief 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?

Explicitly routes the agent: "Use this to discover available API endpoints before calling execute_api." This gives a clear when-to-use condition tied to a named alternative. It lacks an explicit when-not/negative case (e.g., when to skip discovery), so it falls 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 PPN Hub — public APIs over MCP 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