Skip to main content
Glama
30book-mcp

30book-mcp

by sepehr071

Find a publisher by name

sb_find_publisher
Read-onlyIdempotent

Resolve a Persian publisher name to its ID, then pass that ID to book search or publisher lookup tools.

Instructions

Look up publisher ids by name. Pass the id to sb_search(publisher_id=...) or sb_publisher.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPart of the publisher name, Persian, e.g. 'قطره'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds that the result is an id to be reused, but says nothing about ambiguity handling — whether multiple publishers can match a partial name, how many results come back, or what happens on no match. For a fuzzy 'find' tool that is a meaningful gap, so a 3 is appropriate.

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?

Two short sentences with zero filler; the core purpose is front-loaded and the follow-up sentence carries actionable next-step information rather than repetition.

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 rich annotations and no output schema, the definition covers purpose and downstream usage adequately. The remaining hole is return shape — singular id vs. list of candidates — which matters for a partial-match lookup but is a modest omission given the tool's simplicity.

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 explains that 'name' is a partial publisher name in Persian with an example. The description only restates 'by name' and adds no syntax, matching, or length guidance beyond the schema, so baseline 3 applies.

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?

The description uses a specific verb and resource ('Look up publisher ids by name') and clarifies the resolution role by naming the downstream tools sb_search(publisher_id=...) and sb_publisher. It distinguishes itself from those siblings implicitly by operating on a name rather than an id, though it never states that contrast directly.

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 workflow context: this is a name-to-id resolver whose output feeds sb_search(publisher_id=...) or sb_publisher. There is no explicit exclusion ('do not use if you already have an id'), but the intended call situation is easy to infer from the routing sentence.

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