Skip to main content
Glama

Ask Japan Hub

List your MCP server on Ask Japan

hub_register_provider
Idempotent

For service providers: list your public remote MCP server (Streamable HTTP, HTTPS) on Ask Japan so its tools become available to every AI that connects to Ask Japan. The check is automatic: the URL must be public HTTPS, tools/list must work, and tool text must not contain instructions aimed at the AI. Returns approved or rejected with the reason.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "mcp_url": "<mcp_url>",
      "contact_email": "<contact_email>"
    },
    "name": "hub_register_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesService name shown to users
mcp_urlYesPublic MCP endpoint, e.g. https://example.com/mcp
descriptionNoOne or two sentences on what the service does
contact_emailYesWhere we can reach the operator

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), the description discloses that validation is automatic and enumerates the acceptance criteria: public HTTPS, a working tools/list, and no AI-directed instructions in tool text. It also states the response shape (approved/rejected with reason). Remaining gaps are operational — review timing and what happens after approval — rather than contradictions.

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?

Three tight sentences: audience and action first, acceptance checks second, return value last. No filler or redundant restatement of the name.

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?

With no output schema, the description carries the return contract ('approved or rejected with the reason') and the validation rules, which is what an agent needs before submitting. It leaves the post-approval lifecycle and any processing latency unspecified, a minor gap for a 4-parameter submission tool.

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 is 3, but the description adds transport-level meaning to mcp_url beyond the schema's 'Public MCP endpoint': it must be public HTTPS and Streamable HTTP. It adds nothing extra for name, description, or contact_email, which the schema already covers.

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 — listing a public remote MCP server (Streamable HTTP, HTTPS) on Ask Japan — and states the effect: its tools become available to every connected AI. This is clearly distinct from the sibling hub_list_providers, which reads as the read-side counterpart to this registration action.

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 names the intended caller ('For service providers') and implicitly restricts use to operators with a public remote server, which is real context for selection. It does not name an explicit alternative or state when not to use it, so it stops short of full routing 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