Skip to main content
Glama
astroway

astroway-mcp

Official

Exercise Needs

pet_exercise_needs
Read-onlyIdempotent

Calculates daily exercise minutes and suggests activities for pets based on astrological birth chart elements.

Instructions

Element-based daily exercise minutes + recommended activities.

[Group: Pet Astrology]

Example request body: {"date":"1990-05-15","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesBirth date YYYY-MM-DD
timeYesBirth time HH:mm:ss (local)
timezoneOffsetNoUTC offset in hours (e.g. 3 for UTC+3, -5 for EST)
latitudeNoBirth latitude in decimal degrees
longitudeNoBirth longitude in decimal degrees
houseSystemNoHouse system: P=Placidus (default), K=Koch, W=Whole Sign, E=Equal
cityNoCity name (display only)
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, indicating safe, non-mutating operation. The description adds that it returns exercise minutes and activities, but fails to explain that it uses astrological birth data or how results are derived. The example request body includes birth chart parameters, which may confuse agents expecting simple pet data.

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 very concise, consisting of one sentence plus a group tag and example. It is front-loaded and efficient, but the structure could be improved with clearer separation of purpose and usage.

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?

The description is very brief for a tool with 7 parameters and no output schema. It does not explain what 'element-based' means, how exercise minutes are computed, or what the output format is. More context is needed for agents to use this tool effectively.

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%, so all parameters are described in the input schema. The description does not add any additional meaning beyond what the schema already provides. Baseline score 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?

The description states it provides 'element-based daily exercise minutes + recommended activities', which clearly indicates the tool's output. However, it does not explicitly state that it uses birth chart parameters, though the example implies it. The group label 'Pet Astrology' helps contextualize it among sibling tools.

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 explicit guidance on when to use this tool versus alternatives. No mention of prerequisites or when not to use. The description is too brief to provide usage context.

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