Skip to main content
Glama

quote_by_author

Read-onlyIdempotent

Retrieve quotes by a specific author using their name or slug; optionally set a result limit to control how many quotes are returned.

Instructions

Get quotes by a specific author.

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": {
      "author": "<author>"
    },
    "name": "quote_by_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 10)
authorYesAuthor name or slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety and mutability profile is covered. The description adds little behavioral context beyond the retrieval scope, omitting return format, pagination, and any external-API/rate-limit implications.

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?

The description is a single front-loaded sentence with no wasted language. It is appropriately sized for a simple lookup tool.

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?

The tool is simple and the schema plus annotations cover most agent needs, but there is no output schema and the description does not explain the response shape, pagination, or what a returned quote list looks like. That leaves some relevant context unstated.

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 description coverage is 100%, and both parameters are documented in the schema. The description only mentions the author constraint and does not add details such as author-name-vs-slug handling or the limit/default behavior, so the schema does most of the work.

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 states a specific verb and resource ('Get quotes') plus the scope ('by a specific author'), making the core operation clear. It does not explicitly name sibling tools or contrast with quote_search, quote_random, or quote_list_authors, so it falls short of full sibling differentiation.

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?

The phrase 'by a specific author' implies the intended use case, but there is no explicit guidance on when to use this versus quote_search, quote_random, or quote_list_authors. Usage is implied rather than directed.

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

Deploy Server

Other Tools