Skip to main content
Glama
astroway

astroway-mcp

Official

Fate Line

palmistry_fate_line
Read-onlyIdempotent

Analyze the fate line on the palm to reveal insights about career path and life direction.

Instructions

Career, life direction.

[Group: Palmistry (Cheiro)]

Example request body: {}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesRaw JSON body — see the example in the tool description for required fields
Behavior3/5

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

The description adds no behavioral context beyond the annotations, which already indicate it's read-only, non-destructive, and idempotent. While the annotations cover safety, the description does not elaborate on any additional traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short but under-specified. It lacks essential information about the tool's output or expected input, making it insufficiently informative despite its brevity.

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

Completeness2/5

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

With no output schema and many sibling tools, the description is incomplete. It does not explain what the tool returns or how it operates, leaving the agent underinformed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 100% coverage but the 'body' parameter description merely says 'see the example', and the example is an empty object {}. This does not clarify required fields or structure, providing little meaning beyond the schema.

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

Purpose2/5

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

The description 'Career, life direction' is too vague and does not differentiate from sibling palmistry tools like palmistry_head_line or palmistry_life_line. It lacks a specific verb or action, making it unclear what the tool does beyond the name.

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?

No guidance is provided on when to use this tool versus alternatives like other palmistry tools. The description does not mention when to use it, when not to, or suggest alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server