Skip to main content
Glama

AskY Tarot Reading

Personal reading

get_personal_reading_info
Read-onlyIdempotent

Returns a short description of AskY's personal reading (a reading written by the reader herself for one question and sent by email, for adults aged 18 and over) and the address of the page that explains it. Use only when someone asks about a reading written personally for them. Nothing is booked or paid for in the conversation; this tool only returns information and a link.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: "en" for English, "es" for Spanish. Use the language the person is writing in. Defaults to 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 declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context the annotations cannot express: the absence of any booking or payment flow, the fact that only information and a link are returned, and the 18+ audience restriction. It stops short of saying whether the linked page or email content is fetched live.

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 identity and return value are front-loaded in the first sentence, with usage restriction and the no-booking clarification following. It is one dense sentence plus two short clauses with no filler, though the parenthetical definition is lengthy and could be split for faster scanning.

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 enum parameter with full schema coverage and complete annotations, the description covers what the tool is, when to call it, and what it returns — including that a URL is part of the output, which matters given there is no output schema. Only minor gaps remain, such as whether the returned text is static or per-user.

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 single `lang` enum already documents both values and the default-to-English rule. The description says nothing about language selection, so it adds no meaning beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource ('Returns a short description of AskY's personal reading') and then defines that resource — a reading written by the reader herself, for one question, sent by email, for adults 18+ — plus exactly what comes back (description and page address). That definition alone distinguishes it from the tarot-oriented siblings without needing to name them.

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?

It gives an explicit positive trigger ('Use only when someone asks about a reading written personally for them') and a negative constraint ('Nothing is booked or paid for in the conversation; this tool only returns information and a link'). What it does not do is name a sibling for the adjacent case (e.g., a tarot reading question), so routing is inferable but not spelled out.

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