Skip to main content
Glama

Mozaika Books Catalog

list_tropes

List romance trope slugs and labels available in the Mozaika Publications catalog for a locale.

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

Input Schema

NameRequiredDescriptionDefault
langNoLocale code (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden; it does imply a read-only catalog listing, but never says whether the set is exhaustive, how results are ordered, or whether an unsupported lang returns an error or falls back to en. For a simple reference-list tool the gaps are modest but real.

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 with the resource front-loaded and no filler; every clause (catalog, slug/label, locale) carries information.

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 one-optional-parameter read-only listing with no output schema, the description conveys enough: what entities are returned and their scoping. Only loose ends remain, such as result size and behavior for unsupported locales.

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 single lang parameter is already documented as a locale code defaulting to en. The phrase 'for a locale' adds a little meaning by implying the returned labels are localized, but no format or supported-value guidance is added.

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 (list) and a precisely scoped resource: romance trope slugs and labels from the Mozaika Publications catalog. It is clearly a reference-lookup tool distinct from the book-oriented siblings, though it never names those siblings to contrast with.

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?

Usage is only implied by the word 'available' — an agent can infer this is the tool to call before filtering books by trope, but the description gives no explicit when-to-use statement, no prerequisite, and no pointer to related tools such as books_like.

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