Skip to main content
Glama

DinCat — learning and life in Japan

DinCat library: question pages by shelf

list_library
Read-onlyIdempotent

List DinCat's library of ready-made question pages, grouped by shelf: money (take-home pay, staying a dependent, year-end adjustment), visa and residence, Japanese certification exams (FP, IT Passport, Applied Information Technology Engineer), languages (Japanese, English, Chinese) and hard-to-say conversations at work. Each link opens that question in DinCat's chat; no sign-up is needed to try. Use search_library to look up a keyword.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the reply and of the linked pages: ja = Japanese, zh = Simplified Chinese, en = English. Use the user's language.ja
shelfNoOnly this shelf: money, visa, exam, lang or awkward. Omit for all shelves.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: each entry is a link that opens the question in DinCat's chat and no sign-up is required. It still says nothing about pagination, ordering, or result count for a catalog that could be long.

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-loaded with the core action, then the shelf inventory, then the routing hint — a sensible order. The shelf enumeration is long but carries real selection value; little of it is wasted, though the parenthetical examples could be trimmed.

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?

Covers purpose, routing and the nature of returned links, which is most of what a two-optional-param list tool needs. With no output schema, it could say more about the shape of the response (grouping, number of items, link target behavior) for an agent deciding how to present results.

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; the description goes beyond the bare enum values by mapping shelves to their subject matter (exam = FP, IT Passport, Applied IT Engineer; awkward = hard-to-say conversations at work), which helps an agent pick the right shelf. The lang parameter is left entirely to the schema, which is acceptable given its full coverage.

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 and resource ("List DinCat's library of ready-made question pages, grouped by shelf") and enumerates what the shelves actually contain, so an agent knows the scope precisely. It is clearly separable from search_library, which it names as the lookup-style alternative.

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?

Routes keyword lookups to search_library explicitly, giving a clear when-to-use-other rule. It does not state an explicit exclusion for this tool itself (e.g. avoid when the user wants a specific page), but the browse-vs-search split is unambiguous.

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