Skip to main content
Glama

APP NAVI

get_app

slug で 1 件のアプリの詳細(料金・機能・出典・確認日)を取得する。

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": {
      "slug": "<slug>"
    },
    "name": "get_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does useful work by disclosing the returned fields (pricing, features, source, last-checked date), which tells the agent this is a detail-enrichment read. It omits other behavior: whether the call is read-only (only implied by 取得), permission requirements, and not-found handling.

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?

One sentence, front-loaded with the verb and resource, then the returned fields. Nothing is redundant and nothing needs to be read twice.

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 single-parameter read tool with no output schema, naming the returned fields is a good substitute for a return schema. The definition is still thin on slug format and on error/empty behavior, which matter for an agent that may pass an arbitrary identifier.

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 0%, so the schema only says slug is a string. The description clarifies that the slug identifies exactly one app, but never gives the slug format (e.g. package/bundle identifier) or whether it must match a value returned by search_apps.

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?

States a specific verb (取得する / retrieve) and a specific resource (1 件のアプリ) and even enumerates the fields returned (料金・機能・出典・確認日). This clearly separates it from a bulk search like search_apps, though it never names a sibling to make the contrast explicit.

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 phrase 'slug で' implies you must already have a known slug, which is an implicit signal to use search_apps first. However, there is no explicit when-to-use statement, no stated precondition for obtaining the slug, and no mention of what to do when the lookup fails.

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