Skip to main content
Glama
Sign In

Bibooks

by org.bibooks
OverviewDiscussionsAdmin

List languages

list_languages
Read-onlyIdempotent

List every content language books are written in or translated into: its code (used by the other tools), English and native names, and how many public books are translated into it. Optionally render the names in a display locale (e.g. 'es').

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

Input Schema

NameRequiredDescriptionDefault
localeNoLocale for display_name, e.g. 'en', 'es', 'zh'.

Output Schema

NameRequiredDescriptionDefault
itemsYes
localeYesThe locale display_name is rendered in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: it specifies that counts reflect only public books and that names can optionally be localized, which helps set expectations about the result.

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?

The description is a single, front-loaded sentence that packs purpose, return content, and the optional localization behavior without filler. Every clause earns its place.

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

Completeness5/5

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

With an output schema, rich annotations, and only one optional parameter, the description supplies everything an agent needs: what is listed, what each entry contains, and how the locale parameter changes output. No critical gaps remain.

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 coverage is 100%, and the schema already documents the optional 'locale' parameter with examples. The description adds a display-locale example ('es') but otherwise restates what the schema provides, so baseline 3 is appropriate.

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 uses a specific verb ('List') and resource ('content language books are written in or translated into') and spells out the returned fields: code, English/native names, and public-book counts. An agent can immediately tell this is a language enumeration tool, distinct from the book-centric siblings.

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 clear context by noting that the language codes are 'used by the other tools,' which implies when an agent would call this before other operations. It lacks explicit when-not-to-use guidance or named alternatives, but none of the siblings serve the same purpose.

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

All Bibooks toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources