Skip to main content
Glama

Ask Japan Hub

List services on Ask Japan

hub_list_providers
Read-onlyIdempotent

List the third-party services listed on Ask Japan and the tool prefix each one uses.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world call, so the safety profile is covered. The description adds useful context that the result includes a tool prefix per service, but with no output schema it still leaves the response shape (names, count, ordering) unspecified.

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?

A single sentence with no filler, and the key fact (what is listed) is front-loaded before the detail about tool prefixes.

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 zero-parameter listing tool, this is close to sufficient: it states the source and one notable field of the return value. With no output schema, a brief note on what a returned entry looks like (service name plus prefix) would make it fully self-contained.

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 there is nothing for the description to disambiguate; baseline for a no-param tool applies. The description correctly implies the call is unfiltered and global to the hub.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ("List") plus a specific resource ("third-party services listed on Ask Japan") and adds that each entry carries a tool prefix, so an agent knows what it gets back. It does not, however, distinguish itself from the sibling `list_services`, which by name alone looks like it could serve the same discovery role.

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

Usage Guidelines3/5

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

Usage is only implied: mentioning "the tool prefix each one uses" suggests this is the discovery step before invoking other hub tools, but there is no explicit when-to-use or when-not-to-use statement. No alternative (e.g. `list_services`) is named or excluded.

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