Skip to main content
Glama

Search Colours by Concept or Culture

query_conceptual
Read-only

Answers a cultural, historical or material colour question. Returns named archive colours with provenance and cultural context. Works for abstract queries like 'grief' (returns Ophelia Violet, Titan's Grief), 'toxic Victorian pigments' (returns Nightshade Poison Berry Purple, Victorian Arsenic Mirror Silver), or 'the sea at dusk' (returns Evening Sea, Thames Blue Dusk). A vague or personal-sounding query still returns results; result_path in the response states whether this was a 'direct' hit, a 'broadened' retry (relaxed match threshold) or a 'redirected' fallback (dropped an archive restriction or switched to full-corpus semantic search).

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": "query_conceptual"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesThe colour concept or cultural question to search for
archiveNoOptional: restrict to a named archive e.g. 'Japan', 'Pigment', 'OttomanEmpire'
n_resultsNoNumber of results (default 5)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Structured JSON response. Shape varies by tool; most return an 'ok' boolean plus a 'result' or 'results' field with the tool's data payload.",
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "error": {
      -      "type": "string"
      -    },
      -    "ok": {
      -      "type": "boolean"
      -    },
      -    "result": {
      -      "type": [
      -        "object",
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  3. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses real runtime behavior: vague queries are still served, and result_path reports whether the hit was 'direct', 'broadened' (relaxed threshold) or 'redirected' (archive restriction dropped, full-corpus semantic search). That fallback ladder is non-obvious behavior an agent could not infer from the schema, and it is consistent with the read-only annotation.

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?

Purpose is front-loaded in the first sentence, then output shape, then the result_path caveat. The three parenthetical examples are long but each demonstrates a different query register (abstract, historical, evocative), so they earn their space. Slightly denser than necessary for a three-parameter tool.

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?

With an output schema present, the description need not enumerate return fields, and it correctly spends its words on the one non-obvious output signal (result_path). Nothing about invocation is missing. Minor gap: interaction between archive and n_results (e.g. behavior when archive is empty for a query) is unstated.

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 the schema baseline is 3. The description adds meaning by tying the archive parameter to the 'redirected' fallback, where the archive restriction is dropped - a semantic link the schema's plain 'restrict to a named archive' does not convey. n_results receives no added nuance, keeping it from a 5.

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?

"Answers a cultural, historical or material colour question" gives a specific verb and resource, and "returns named archive colours with provenance and cultural context" pins down the output. The three worked examples make the abstraction concrete. It does not name a sibling (e.g. archive_search or historical_colour_query) to separate itself from, so it falls short of a 5.

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 examples ('grief', 'toxic Victorian pigments', 'the sea at dusk') clearly signal the class of query this tool is for, and the note that vague queries still return results sets expectations about when it remains useful. There is no explicit when-not guidance or named alternative for cases like a hex lookup or a plain keyword archive search.

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