Skip to main content
Glama

Dream Interpreter AI

Common dream symbols

common_dream_symbols
Read-onlyIdempotent

The symbols that come up most often in dreams written in English on Dream Interpreter AI, most common first, each with the start of its meaning and its page.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "common_dream_symbols"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description still adds real value by disclosing result ordering, item contents ('start of its meaning and its page' – i.e. truncated meanings, not full entries) and the English-only corpus; a lack of pagination/limit information keeps this at a 3 rather than a 4.

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?

A single front-loaded sentence that names the resource, the ordering, the per-item contents and the corpus scope with no filler. It is dense but every clause carries information, so no trimming is obviously warranted.

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?

With zero parameters, no nested objects and no output schema, the description's job is to convey what comes back; it does that by stating the ordered list, the truncated meaning preview and the presence of a page reference. Nothing an agent needs in order to call or interpret this tool 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?

There are zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No schema detail is repeated or contradicted.

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 gives a specific resource (the most frequent dream symbols) plus the ordering rule ('most common first') and the scope ('dreams written in English on Dream Interpreter AI'), so an agent knows this is a ranked browse list rather than a search. It stops short of naming the sibling tools it displaces (search_dream_symbols, lookup_dream_symbol), which keeps it from 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use statement and no named alternative. The absence of parameters implies a 'browse popular symbols' entry point, but that is inference rather than guidance, and nothing tells the agent to prefer lookup/search when it already has a symbol name.

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