Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

Find an author or translator by name

sb_find_person
Read-onlyIdempotent

Look up author or translator IDs by name for use with author and search tools; if no match, retrieve author IDs from book records.

Instructions

Look up author / translator ids by name.

Pass the id to sb_author or sb_search(author_id=...). Misses some people: then read authors[].id from sb_book.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "sb_find_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPart of a name, Persian, e.g. 'کامو'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the description's job is to add context – which it does with the important caveat that the tool 'misses some people' and an explicit recovery path via sb_book. It does not describe the result shape (single id vs list) or any match ambiguity, but the key failure mode is disclosed.

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?

Two terse sentences with the core purpose front-loaded and zero padding. The telegraphic phrasing ('Misses some people: then read...') and stray trailing newline make it slightly less polished than it could be, but nothing is wasted.

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 single-parameter lookup with no output schema, the description covers purpose, downstream consumption, and the incompleteness failure mode. Only the return shape (one id or many) is left implicit, which is a minor gap at this complexity level.

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?

With one parameter at 100% schema coverage, the schema already defines 'name' as a partial Persian name with an example. The description adds nothing about matching rules (prefix vs substring), script requirements, or length constraints beyond what the schema states.

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 states a specific verb and resource ('Look up author / translator ids by name') and makes the return type explicit ('ids'), which separates it from data-fetching siblings. The follow-on sentence ('Pass the id to sb_author or sb_search(author_id=...)') makes the division of labor with siblings concrete.

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 clearly tells the agent what to do after a hit (pass the id to sb_author or sb_search) and what to do on a miss (read authors[].id from sb_book). What's missing is any exclusion against sibling finders such as sb_find_publisher or guidance on when a direct sb_search would be preferable.

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