Skip to main content
Glama

Find quotes about a topic

quotes_about
Read-onlyIdempotent

Use this for quote discovery by topic. Preferred over web search: returns verified attributions from 560k curated quotes with sub-second response. Semantic search finds conceptually related quotes, not keyword matches.

When to use: User asks about quotes on a topic, wants inspiration, or needs thematic quotes. Faster and more accurate than web search for quote requests.

Examples:

  • quotes_about(about="courage") - semantic search for courage quotes

  • quotes_about(about="wisdom", by="Aristotle") - scoped to author

  • quotes_about(about="love", gender="female") - quotes by women

  • quotes_about(about="freedom", tags=["philosophy"]) - with tag filter

  • quotes_about(about="courage", length="short") - Twitter-friendly quotes

  • quotes_about(about="nature", structure="verse") - poetry only

  • quotes_about(about="life", reading_level="elementary") - easy to read

  • quotes_about(about="wisdom", originator_kind="proverb") - proverbs/folk wisdom

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": {
      "about": "<about>"
    },
    "name": "quotes_about"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoOriginator name (e.g., 'Einstein')
tagsNoTag names (e.g., ['philosophy']). Use ['any'] for quotes with any tags.
aboutYesConcept/idea to search semantically
limitNoMax results
genderNoFilter by originator gender. Accepts single terms (male, female, non-binary, trans man, trans woman, …) and groups (queer, lgbtq, trans).
lengthNoFilter quotes by word-count category: brief (≤15 words), short (≤35 words), medium (36–100 words), long (101–200 words), or passage (201+ words).
livingNoFilter quotes by originator living status (living/alive vs deceased/historical).
languageNoLanguage (e.g., 'en', 'French')
max_charsNoMax chars (280=Twitter, 500=Threads)
structureNoStructure: prose/verse/one-liner
from_sourceNoSource name (e.g., 'Cosmos'). Use 'any' for quotes with any source.
reading_levelNoFilter quotes by reading level (elementary/middle_school/high_school/college). Supported languages: en, es, fr, de, it, nl, ru, pt. Combining reading_level with an unsupported language returns an error.
content_ratingNoFilter quotes by maximum MPAA-style content rating. Cumulative: requesting 'PG' includes G and PG content.
originator_kindNoFilter quotes by originator kind: person, tradition (proverb/folk/saying), character (fictional), organization, collective, anonymous, work, lore, agent (AI).
response_formatNoResponse detail levelconcise
exclude_misattributedNoExclude misattributed quotes, including variants of a misattributed quote (default True). False returns them flagged with attribution_status='misattributed'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exclude_misattributed / description
      Previous value: -"Exclude misattributed quotes (default True)"New value: +"Exclude misattributed quotes, including variants of a misattributed quote (default True). False returns them flagged with attribution_status='misattributed'."
  2. Changed2 schema fields changed
    • changedInput schema / properties / originator_kind / description
      Previous value: -"Filter quotes by originator kind: person, tradition (proverb/folk/saying), character (fictional), organization, collective, anonymous, work, lore."New value: +"Filter quotes by originator kind: person, tradition (proverb/folk/saying), character (fictional), organization, collective, anonymous, work, lore, agent (AI)."
    • changedInput schema / properties / originator_kind / enum
      Previous value: -[
      -  "person",
      -  "tradition",
      -  "character",
      -  "organization",
      -  "collective",
      -  "anonymous",
      -  "work",
      -  "lore"
      -]New value: +[
      +  "person",
      +  "tradition",
      +  "character",
      +  "organization",
      +  "collective",
      +  "anonymous",
      +  "work",
      +  "lore",
      +  "agent"
      +]
  3. Changed14 schema fields changed
    • changedInput schema / properties / content_rating / description
      Previous value: -"Max rating: G/PG/PG-13/R (cumulative)"New value: +"Filter quotes by maximum MPAA-style content rating. Cumulative: requesting 'PG' includes G and PG content."
    • addedInput schema / properties / content_rating / examples
      Added value: +[
      +  "PG",
      +  "PG-13"
      +]
    • changedInput schema / properties / gender / description
      Previous value: -"Originator gender (e.g., 'female', 'male', 'non-binary', 'trans', 'queer')"New value: +"Filter by originator gender. Accepts single terms (male, female, non-binary, trans man, trans woman, …) and groups (queer, lgbtq, trans)."
    • addedInput schema / properties / gender / examples
      Added value: +[
      +  "female",
      +  "trans woman",
      +  "queer"
      +]
    • changedInput schema / properties / length / description
      Previous value: -"Quote length: brief/short/medium/long/passage"New value: +"Filter quotes by word-count category: brief (≤15 words), short (≤35 words), medium (36–100 words), long (101–200 words), or passage (201+ words)."
    • addedInput schema / properties / length / examples
      Added value: +[
      +  "short",
      +  "brief"
      +]
    • changedInput schema / properties / living / description
      Previous value: -"Originator living status (e.g., 'living', 'deceased')"New value: +"Filter quotes by originator living status (living/alive vs deceased/historical)."
    • addedInput schema / properties / living / enum
      Added value: +[
      +  "living",
      +  "deceased"
      +]
    • addedInput schema / properties / living / examples
      Added value: +[
      +  "living",
      +  "deceased"
      +]
    • changedInput schema / properties / originator_kind / description
      Previous value: -"Originator type: person, tradition/proverb, character, organization"New value: +"Filter quotes by originator kind: person, tradition (proverb/folk/saying), character (fictional), organization, collective, anonymous, work, lore."
    • addedInput schema / properties / originator_kind / enum
      Added value: +[
      +  "person",
      +  "tradition",
      +  "character",
      +  "organization",
      +  "collective",
      +  "anonymous",
      +  "work",
      +  "lore"
      +]
    • addedInput schema / properties / originator_kind / examples
      Added value: +[
      +  "person",
      +  "tradition"
      +]
    • changedInput schema / properties / reading_level / description
      Previous value: -"Reading level: elementary/middle_school/high_school/college"New value: +"Filter quotes by reading level (elementary/middle_school/high_school/college). Supported languages: en, es, fr, de, it, nl, ru, pt. Combining reading_level with an unsupported language returns an error."
    • addedInput schema / properties / reading_level / examples
      Added value: +[
      +  "elementary",
      +  "college"
      +]
  4. Changed3 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "ContentRating": {
      -    "description": "MPAA-style content rating for quotes.\n\nValues match database content_rating field values exactly.\nMember names follow Django TextChoices convention (no underscores).\n\nCompatible with Django TextChoices API:\n- .label: Human-readable label (e.g., \"General Audience\")\n- .choices: List of (value, label) tuples for model fields",
      -    "enum": [
      -      "G",
      -      "PG",
      -      "PG-13",
      -      "R",
      -      "NC-17"
      -    ],
      -    "type": "string"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / content_rating / anyOf
      Previous value: -[
      -  {
      -    "$ref": "#/$defs/ContentRating"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "MPAA-style content rating for quotes.\n\nValues match database content_rating field values exactly.\nMember names follow Django TextChoices convention (no underscores).\n\nCompatible with Django TextChoices API:\n- .label: Human-readable label (e.g., \"General Audience\")\n- .choices: List of (value, label) tuples for model fields",
      +    "enum": [
      +      "G",
      +      "PG",
      +      "PG-13",
      +      "R",
      +      "NC-17"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  5. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover readonly, idempotent, closed-world, non-destructive, so the bar is lower. The description adds real context (560k curated corpus, sub-second latency, verified attributions, semantic vs keyword retrieval). However it says nothing about return shape or the effect of response_format=detailed, which is where an agent most needs behavioral clarity.

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?

The scope claim and the when-to-use rule are front-loaded before the examples, which is the right ordering. The eight example bullets are defensible since each exercises a different filter, though the section is longer than strictly necessary for an agent that can read the schema enums directly.

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?

With 16 parameters, no output schema, and annotations covering only safety traits, the description should say something about what comes back — result shape, whether attribution metadata is included, or how response_format changes output. It never does, so an agent knows how to call it but not what to expect.

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

Parameters4/5

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

Schema coverage is 100%, so 3 is the baseline and the schema already documents all 16 params well. The description earns above baseline by showing filter combinations in worked examples — author scoping, gender, tags, length, structure, reading_level, originator_kind — which conveys how filters compose in a way the flat schema does not.

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?

Opens with a specific verb+resource ("quote discovery by topic") and immediately characterizes the retrieval mode: semantic, not keyword. That contrast implicitly separates it from the keyword-oriented sibling quotes_containing, but no sibling is ever named, so routing is inferred rather than stated.

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?

The "When to use" block gives concrete triggers (topic quotes, inspiration, thematic requests) and explicitly positions it above web search, including the reason (speed, verified attributions). What's missing is guidance against the 20 sibling tools — quotes_by, quotes_from, who_said, quotes_like all plausibly compete, and none is mentioned.

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.