Skip to main content
Glama

Search authors

search_authors
Read-onlyIdempotent

Find authors by name. Returns up to 5 matches, each linking to the author page.

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": {
      "query": "<query>"
    },
    "name": "search_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes3 to 200 characters, with at least 3 letters or digits.

Output Schema

NameRequiredDescriptionDefault
moreAtYesWhere to keep browsing on listofbooks.net.
resultsYesMatching catalog entries. Each links to its page.
withheldYesMatches left out because the daily limit of distinct pages was reached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a safe, idempotent, closed-world read. The description adds a genuinely useful behavioral detail beyond them: results are capped at 5 matches linking to author pages, which tells the agent the result set may be incomplete. It does not discuss match fuzziness or ordering.

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 action is front-loaded and the result cap follows immediately. Nothing could be removed without losing 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 single-parameter search tool with annotations and an output schema, this covers the essentials: what it does, what it returns, and a result limit. The only notable omission is whether matching is exact or partial, which would help the agent decide to broaden a query.

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%, so the query constraints (3–200 chars, at least 3 letters or digits) are fully documented structurally. The description only adds that the query is interpreted as a name, which is a marginal semantic gain over the schema. 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?

States a specific verb and resource ('Find authors by name'), making it immediately distinguishable from the series-oriented siblings. It does not explicitly contrast itself with those siblings, but the resource difference is self-evident from the name and description.

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 implied by 'by name' – the agent knows this takes a name query rather than an ID or title. There is no explicit guidance on when to prefer this over alternatives or on refining a query when results are truncated.

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