Skip to main content
Glama

APP NAVI

get_ranking

★評価に基づくランキング。評価が3件以上のアプリだけが順位に載る(ranked)。評価が少ないアプリは rising に件数だけ出る。順位は評価だけで決まり、広告や掲載料は関係しない。Ranking by user star ratings (3+ ratings required).

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_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryNoカテゴリー slug(省略すると総合)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.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 burden and usefully discloses that only apps with 3+ ratings are ranked, low-rated apps appear in rising with counts only, and ranking is not influenced by ads or fees. It still omits some operational details such as pagination behavior or exact response structure.

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?

The description is short and front-loads the ranking basis and eligibility rule. The English sentence partly repeats the opening Japanese sentence, but the overall structure remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter ranking tool with no output schema, the description explains key eligibility and ranking behavior but does not fully describe return fields or how ranked and rising entries are shaped. It is adequate but leaves clear gaps about result structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: the category parameter has schema documentation, but limit has only default/min/max constraints and no textual description. The description itself does not explain either parameter or add meaning beyond what the schema already provides for category.

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 clearly states that this tool returns a ranking based on user star ratings and specifies the 3+ rating eligibility rule. It does not explicitly distinguish itself from siblings such as search_apps, so it is clear but lacks sibling differentiation.

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?

The description implies usage by explaining ranked versus rising apps, but it does not explicitly say when to use this tool instead of search_apps or other siblings. The guidance is enough to infer that it is for rankings, not general search.

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