Skip to main content
Glama

Dream Interpreter AI

Dreams by country

dreams_by_country
Read-onlyIdempotent

What people in a country dream about, from real dreams on Dream Interpreter AI: the country's standout symbol (much more common there than in the rest of the world) and its most common symbol, with how many dreams were counted. Without a country, every country with enough dreams.

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

Input Schema

NameRequiredDescriptionDefault
countryNoA country's English name ("Brazil") or two-letter ISO code ("BR"). Leave it out for every country.

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?

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context beyond that: it discloses the two returned fields and the 'enough dreams' threshold, but leaves the actual count threshold and result size unspecified.

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?

Two sentences, front-loaded with what the tool returns and followed by the default-scope clause. Efficient, though the parenthetical about 'much more common there than in the rest of the world' is slightly wordy and the sentence structure is a bit dense.

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 single optional-parameter read tool with full schema coverage and no output schema, the description covers the return shape (standout symbol, most common symbol, counts) and both invocation modes. Only the undefined 'enough dreams' threshold and the result ordering/size keep it from being complete.

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 coverage is 100% and the schema already documents that country accepts an English name or ISO code and is optional. The description reinforces the omission behavior ("Without a country, every country...") but adds no new format or matching semantics such as case-insensitivity or handling of unknown names, 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?

States a specific resource and scope: per-country dream statistics, specifically the standout symbol and the most common symbol with dream counts. It is distinguishable from lookup/search/common-symbol siblings, though it never names them explicitly to sharpen the contrast.

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 implies usage via the optional-country behavior ("Without a country, every country with enough dreams"), which hints at both a single-country lookup and an all-countries listing mode. It does not state when to prefer this over common_dream_symbols or search_dream_symbols, so the agent must infer the routing.

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