Skip to main content
Glama

Chart twins

find_chart_twins
Read-onlyIdempotent

Finds famous people, among those Zodiacs publishes charts for, whose Sun sign, Moon sign or both match the person's, with a link to each chart. It fits a question about which famous people share someone's sign or chart. A birth date alone compares the Sun only; the Moon needs the birth time and time zone. It searches only the people Zodiacs publishes. It refuses a birth date less than 13 years ago. Its share link carries the signs and never the birth date.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "birthDate": "<birthDate>"
    },
    "name": "find_chart_twins"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeNoThe birth time on the local clock, if known. Needs zone. Without it only the Sun is compared.
zoneNoThe birthplace's time zone, such as Europe/London. Needed with a time.
latitudeNoThe birthplace's latitude, if known. Give it with longitude.
birthDateYesThe birth date, such as 1997-03-15.
longitudeNoThe birthplace's longitude, if known, for birth times before standard time.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses three non-obvious behaviors: the restriction to Zodiacs-published people, a refusal rule for birth dates under 13 years old, and that the share link carries signs but never the birth date. These are exactly the kind of constraints an agent cannot infer from structured fields.

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?

Four short sentences with the capability first, then fit, then input requirements, then policy constraints. Every sentence carries distinct information and none repeats the name or title.

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

Completeness5/5

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

With an output schema present, return-shape detail is unnecessary, and the description instead covers what the agent needs: scope of the search pool, the input combination that unlocks Moon matching, the refusal threshold, and privacy behavior of the output link. Nothing material is left unstated.

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 the Sun-only vs. time+zone-for-Moon relationship and the lat/long pairing. The description restates the time/zone requirement at a high level but adds no syntax, format, or edge-case detail beyond the schema, so the 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?

States a specific verb and resource – finding famous people among Zodiacs' published charts whose Sun and/or Moon sign matches – and scopes it explicitly ('It searches only the people Zodiacs publishes'). This clearly separates it from single-chart siblings like get_famous_chart or get_natal_chart without needing their schemas.

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?

Gives a concrete use case ('a question about which famous people share someone's sign or chart') and explains the input precondition that decides whether Moon matching happens (time plus zone required; date alone compares Sun only). It does not name an alternative tool or state when not to use it, so it falls short of full routing guidance.

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.