Dream Interpretation MCP Server by RoxyAPI

List and search dream symbols - Dream dictionary API

get_dreams_symbols

Read-only

Browse and search our complete dream interpretation dictionary containing 2,000+ dream symbols with psychological meanings. Find dream meanings for animals (snake dreams, spider dreams, dog dreams), common scenarios (falling dreams, flying dreams, being chased, drowning), people (dreams about mother, father, baby, ex), objects (car, house, water, fire), emotions (fear, anxiety, love), body parts (teeth falling out, hair, eyes), colors, numbers, and abstract concepts. Filter by starting letter for A-Z navigation or search by keyword to find what your dreams mean.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Search query to match against symbol names and meanings. Case-insensitive.
`limit`	No	Maximum items to return per page. Range: 1-50, default 20.
`letter`	No	Filter symbols by starting letter (a-z). Case-insensitive.
`offset`	No	Number of items to skip for pagination. Default 0.
`compact`	No	Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	Yes
`total`	Yes
`offset`	Yes
`symbols`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 23, 2026
- addedInput schema / properties / offset / default
```
Added value: +0
```
- addedInput schema / properties / offset / minimum
```
Added value: +0
```
Changed3 schema fields changedSep 20, 2026
- removedInput schema / properties / offset / default
```
Removed value: -0
```
- removedInput schema / properties / offset / minimum
```
Removed value: -0
```
- changedInput schema / properties / offset / type
```
Previous value: -[
-  "integer",
-  "null"
-]New value: +"integer"
```

Changed1 schema field changedSep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "limit": {
+      "type": "number"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "symbols": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "letter": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "letter"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "limit",
+    "offset",
+    "symbols"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedAug 17, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedInput schema / properties / compact / description

Previous value: -"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."New value: +"Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {\"__cols\":[names],\"__rows\":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens."

Changed1 schema field changedAug 2, 2026
- changedInput schema / properties / offset / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

Changed1 schema field changedJul 22, 2026

changedInput schema / properties / compact / description

Previous value: -"Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false."New value: +"Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {\"__cols\":[field names],\"__rows\":[[values]]}, so each field name is sent once instead of once per row. Fully lossless (no field or value is dropped or changed) and typically 40 to 52 percent fewer tokens on large results. Prefer true whenever token or inference cost matters. Default false returns standard indented JSON."

Changed1 schema field changedJul 22, 2026

addedInput schema / properties / compact

Added value: +{
+  "default": false,
+  "description": "Return the same data in a token-optimized compact shape (minified, with same-shaped arrays encoded columnar) to reduce LLM token cost. Lossless: no fields are dropped. Default false.",
+  "type": "boolean"
+}

First observedJul 8, 2026

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 and destructiveHint=false, so the safety profile is covered. The description adds useful scope context (2,000+ symbols, broad category coverage) but does not disclose extra behavioral details such as pagination behavior, how results are ordered, or how q interacts with letter. This is acceptable but not exceptional given the annotations present.

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 description is front-loaded with the action and resource, and the second sentence gives valuable real-world examples for matching dream topics. It is somewhat long, but the examples help an agent recognize relevant queries; no sentence is tautological or purely redundant.

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?

Combined with a fully documented input schema, output schema, and read-only annotations, the description provides enough context for correct invocation. The main remaining gap is the lack of explicit guidance on choosing among sibling tools and how q and letter behave when combined, but this is minor against the strong structured metadata.

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%, with each parameter already well documented (ranges, defaults, case-insensitivity, compact shape semantics). The description only reinforces q and letter usage and adds no new parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 action ('Browse and search'), a resource ('complete dream interpretation dictionary'), and gives concrete examples of content types. It stops short of explicitly distinguishing itself from siblings such as get_dreams_symbols_id or get_dreams_symbols_random, although its broad list/search scope is inferable from the wording.

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 description gives clear usage context: use keyword search or A-Z letter filtering to find dream meanings. However, it never names alternatives like get_dreams_symbols_id or get_dreams_symbols_letters or states when those should be preferred, leaving tool selection partly to inference.

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

All Dream Interpretation MCP Server by RoxyAPI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?