Skip to main content
Glama

Rosmaryn

List the free Rosmaryn calculators

list_calculators
Read-only

List the free online calculators of Rosmaryn (Human Design Body Graph, birth chart, transits, numerology, and more) with their links.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the results (default en).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes that results come 'with their links' and that the calculators are free/external, which is useful return-shape context, but it says nothing about result count, ordering, or whether the list is static versus dynamic.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the parenthetical examples earn their place by making the tool's scope concrete without adding redundant prose.

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 simple read-only catalog tool with one fully documented optional parameter and no output schema, the description covers what it returns (a list with links). It could be slightly more complete by noting the result is a fixed catalog filtered by language, but nothing essential is missing.

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?

The single optional language parameter is fully documented in the schema (enum of six codes, default en), so the schema already carries the semantics. The description adds no meaning about the parameter — it never mentions localization or that results are language-dependent — leaving it at the baseline.

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?

Specific verb ('List') plus specific resource ('free online calculators of Rosmaryn'), with concrete examples (Body Graph, birth chart, transits, numerology) that tell the agent exactly what content to expect. It does not explicitly contrast itself with the siblings search_encyclopedia or upcoming_sky_events, but the catalog-listing framing is distinguishable from a search or event feed.

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?

Usage is only implied: an agent can infer this is a discovery/catalog tool, but the description never states when to call it, whether it should precede other tools, or whether any prerequisites exist. No exclusions or alternative-routing guidance are given.

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