Skip to main content
Glama

On-Demand-Books

by io.github.gmlewis

On-Demand-Books: Suggest Available Names

suggest_names

Suggest first names for which personalized puzzle books are likely available. Use this when a user is unsure of a spelling, wants gift-recipient ideas, or only has part of a name. Returns popular available names, optionally filtered by a case-insensitive prefix. To confirm a specific name has matching books, follow up with search_books.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of suggestions to return (default 20, max 100).
prefixNoOptional name prefix to complete (e.g. 'su' -> 'Susan', 'Susie', 'Suzanne'). If omitted, returns a curated list of popular names.

TDQS

A4.6/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It describes return behavior (popular available names, optional prefix filtering) and case-insensitivity. Lacks details on permissions or rate limits, but acceptable for a suggestion tool.

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?

Three sentences front-load purpose and usage, with no wasted words. Structure is logical: purpose, context, parameter info, and sibling link.

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?

No output schema, but description does not specify return format (e.g., array of strings). Agent may need to infer structure. Adequate for a simple suggestion tool but could improve.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by explaining prefix as case-insensitive and providing an example. It also clarifies default behavior when prefix is omitted.

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?

Description clearly states the tool suggests first names for puzzle books. It uses specific verbs and resources, and distinguishes from sibling tools by directing to search_books for confirmation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: when unsure of spelling, needs gift ideas, or has partial name. Also clarifies when not to use (for confirmation) and directs to search_books.

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

All On-Demand-Books toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Each tool has a distinct purpose: refreshing a specific book's details, searching by name, and suggesting names. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_book, search_books, suggest_names. The naming is uniform and predictable.

Tool Count4/5

With only 3 tools, the server is lean but covers the core workflow of discovering and referencing books. It could benefit from additional tools for browsing or managing books, but the count is appropriate for a focused domain.

Completeness4/5

The tool set covers the key operations: searching by name, getting suggestions when unsure, and refreshing book details. Minor gaps exist (e.g., no tool for listing all books or managing purchases), but the surface is largely complete for the stated purpose.

Resources