Skip to main content
Glama

Dream Interpreter AI

Search dream symbols

search_dream_symbols
Read-onlyIdempotent

Symbol names in the dream dictionary that contain a word, those starting with it first, up to 20. For finding the exact name to look up, or the symbols that share a word ("teeth" finds "teeth falling out" and others).

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

Input Schema

NameRequiredDescriptionDefault
queryYesA word or part of a word, in English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world and non-destructive behavior, so the bar is lower; the description still adds real value by disclosing substring matching, prefix-first ordering, and a 20-result cap. Undisclosed details such as case sensitivity and empty-result handling are minor gaps for a read-only search.

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 sentences with zero waste: result shape and count are front-loaded, then the two intended uses with a parenthetical example that earns its place. Nothing is repeated from the schema or annotations.

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 one-parameter search with no output schema, the description adequately conveys what comes back (names only, ordered, max 20). It does not say whether the match is case-insensitive or whether the full symbol text is returned, but nothing essential to calling it correctly is missing.

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% and the single 'query' parameter is already documented as a word or partial word in English. The description nevertheless adds semantics the schema does not: the value is matched as a substring anywhere in the symbol name, and prefix matches are ranked first.

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 names the specific resource (symbol names in the dream dictionary) and the exact matching operation (names containing a word, prefix matches ranked first, capped at 20). The phrase 'For finding the exact name to look up' implicitly positions it ahead of a lookup step, but no sibling tool is named explicitly, so differentiation from lookup_dream_symbol and common_dream_symbols 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?

Gives two concrete use cases: resolving an exact symbol name, and discovering symbols that share a word, with a worked example ('teeth' -> 'teeth falling out'). It lacks an explicit when-not or a named alternative for retrieving full symbol content, but the context is unusually clear for a search tool.

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