Skip to main content
Glama

Dream Interpreter AI

Look up a dream symbol

lookup_dream_symbol
Read-onlyIdempotent

The dream dictionary's entry for one symbol: what it means in a dream, the countries where it's the standout or most common symbol in real dreams, a few shared dreams about it, and the link to its page. When there's no entry by that name, the closest symbol names are returned instead.

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": {
      "symbol": "<symbol>"
    },
    "name": "lookup_dream_symbol"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesThe symbol, as a word or short phrase in English: "snake", "teeth falling out", "ex". Singular works best.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: it enumerates what the response contains and, importantly, discloses the fuzzy-miss behavior (nearest names instead of an empty result or error), which an agent could not predict from annotations alone.

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, front-loaded with the resource being fetched, followed by the exact contents. No filler, no restatement of the title, and the fallback clause is compressed into one tail sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-shape burden — and it does, naming meaning, countries of prominence, shared dreams, and page link, plus the no-entry fallback. For a one-parameter, read-only lookup this covers everything an agent needs to call it and interpret the result.

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 the single parameter is already documented with examples and the "singular works best" hint. The description only echoes "one symbol" and adds no syntax, casing, or normalization guidance beyond the schema, so the baseline of 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?

The description states a specific verb+resource ("the dream dictionary's entry") and scopes it to "one symbol", which implicitly contrasts with the lookup-by-many siblings (search_dream_symbols, common_dream_symbols). It never names those alternatives, so an agent must infer the boundary rather than read it, keeping this below 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied — you call it when you have a concrete symbol name and want its meaning — and the fallback case ("when there's no entry by that name, the closest symbol names are returned") usefully tells the agent how to recover. There is no explicit when-not guidance or named alternative for broad/browse queries, so the routing decision is left to inference.

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