Skip to main content
Glama
mrslbt

rakuten-mcp

by mrslbt
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Rakuten Books (Computer Software)

books_software_search
Read-onlyIdempotent

Search Rakuten Books for computer software by title, target OS, or JAN, returning OS, label, price, and review data.

Instructions

Search Rakuten Books for computer software by title, target OS (e.g., 'Windows', 'macOS'), or JAN (at least one; no free-text keyword, use books_total_search for that). Returns software details with target OS, label, JAN, list price, and review stats.

[JA] 楽天ブックスでPCソフトウェアを、タイトル・対応OS(例: 'Windows', 'macOS')・JANで検索します(いずれか必須。フリーワード検索は books_total_search)。対応OS、レーベル、JAN、定価、レビューを含む詳細を返します。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
osNoTarget OS (e.g., 'Windows', 'macOS'). 対応OS。
janNoJAN code. JAN。
hitsNoNumber of results per page (1–30, default 10). 1ページあたりの取得件数(1〜30、デフォルト10)。
pageNoPage number (1+, default 1). ページ番号(1以上、デフォルト1)。
sortNoSort order. 並び順。standard
titleNoSoftware title. ソフトウェア名。
booksGenreIdNoRestrict to a specific Books genre (3-character IDs, hierarchical). Use books_genre_search to discover. ジャンルIDで絞り込み(books_genre_search で取得)。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • removedInput schema / properties / keyword
      Removed value: -{
-  "description": "Free-text keyword. キーワード。",
-  "title": "Keyword",
-  "type": "string"
-}
  2. Addedv1.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety is covered. The description adds genuinely non-schema context: the 'at least one of title/OS/JAN' constraint (schema lists 0 required params) and the shape of returned fields (target OS, label, JAN, list price, review stats). No contradiction with annotations.

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?

Front-loads the purpose, then the constraint and alternative, then the return fields; the JA mirror adds value for the target locale rather than padding. No wasted sentences, though the doubled bilingual text is somewhat long.

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 7-param, no-output-schema read tool, the description covers the core use case, the input constraint, the alternative tool, and the returned fields. Minor gaps remain around pagination and the sort/genre params, but nothing essential to correct invocation is missing.

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 100%, so each parameter is already documented. The description only reinforces title/OS/JAN and says nothing about hits, page, sort, or booksGenreId, adding no syntax or meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb (Search) and a precise resource (Rakuten Books computer software), and explicitly distinguishes itself from books_total_search for free-text queries. An agent can tell this apart from books_book_search, books_game_search, etc. without opening any schema.

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?

Gives clear when-to-use (search by title, OS, or JAN, at least one required) and names an explicit alternative (books_total_search) for free-text. It does not cover the relationship to books_genre_search for the booksGenreId param or to the other media-type searches, so routing is clear but not exhaustive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools