Skip to main content
Glama

get_listing_info

How an AI product gets listed on Hokai: today's one-time price, what a
listing includes, and the free badge route. Use this before buy_listing,
or to answer "how do I get my AI tool listed on Hokai?".

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/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 it does signal that this is a purely informational lookup by framing the result as pricing and listing mechanics, not an action. It discloses the substantive content of the response (price, inclusions, badge route) without stating side effects, which is reasonable for an obvious read-only info tool.

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?

Two sentences, front-loaded with the subject matter and followed by the routing condition. There is no filler, and the enumerated contents make the value of calling it immediately clear.

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-argument tool with no output schema and no annotations, the description adequately substitutes by listing what the response covers. A note on whether pricing is currency-specific or how current it is would close the remaining gap, but an agent has enough to call it 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 and the description correctly spends no words on arguments. The baseline for a parameterless tool is a 4, and nothing here misleads about inputs.

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 names the specific resource (how an AI product gets listed on Hokai) and enumerates what the answer contains: today's one-time price, what a listing includes, and the free badge route. This is far more than a restatement of the name and lets an agent distinguish it from transactional siblings like buy_listing or submit_listing.

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 gives an explicit trigger ('use this before buy_listing') and a user-intent trigger (answering 'how do I get my AI tool listed on Hokai?'). No when-not-to-use clause or mention of the submission path is provided, but the positive guidance is concrete and names the relevant alternative.

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