Skip to main content
Glama

Overlay: Together

Tandem name for two birthdays

tandem_name
Read-onlyIdempotent

Given two people's birthdays, works out the signs of the chart the two of them make together (the composite chart: Sun, Moon and Venus) and the pair's Tandem name, one of 144 names for a composite Sun and Moon. Works for partners, friends and family. Both people must be 18 or over. Birthdays alone are enough. Optionally add each person's birth time and birthplace: with both, the Moon is settled and the rising sign comes back too. Names aren't part of the input, and Overlay stores nothing. When the Moon could be in two signs, more than one name comes back, the likeliest first.

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": {
      "birthday_a": "<birthday_a>",
      "birthday_b": "<birthday_b>"
    },
    "name": "tandem_name"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_aNoOptional. The first person's birth time on the 24-hour clock, as HH:MM. Needs place_a.
time_bNoOptional. The second person's birth time on the 24-hour clock, as HH:MM. Needs place_b.
place_aNoOptional. The first person's birthplace: a town or city with its region or country, such as Chicago, Illinois.
place_bNoOptional. The second person's birthplace: a town or city with its region or country.
birthday_aYesThe first person's birthday, as YYYY-MM-DD.
birthday_bYesThe second person's birthday, as YYYY-MM-DD.
time_a_is_approximateNoOptional. True when time_a is a rough time (within about two hours). A rough time narrows the Moon but gives no rising sign.
time_b_is_approximateNoOptional. True when time_b is a rough time (within about two hours).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description goes further by disclosing that names are not part of the input, that nothing is stored, and that ambiguous Moon positions produce multiple names with the likeliest first — behavioral facts no annotation conveys. It stops short of describing the response shape in any structured way, which keeps it off a 5.

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?

Front-loaded with the core purpose and the output, followed by eligibility, optional-input effects, and the ambiguity rule — a sensible order with little waste. A couple of sentences overlap slightly ('Birthdays alone are enough' vs 'Names aren't part of the input'), but nothing is padded or redundant enough to obscure the point.

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?

With 8 parameters, no output schema, and no nested structures, the description carries the return-value burden and does so adequately by naming the chart bodies returned and explaining the multi-name case. A minor gap is that the exact shape of the response (how names, Sun, Moon and rising sign are presented) is left to discovery.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema alone does not: supplying both birth time and birthplace settles the Moon and returns the rising sign, whereas a rough time only narrows the Moon. That interaction between time_a/place_a and time_a_is_approximate is genuinely useful beyond the field-level descriptions.

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?

States a specific verb and resource: given two birthdays, it computes the composite chart (Sun, Moon, Venus) and the pair's Tandem name from 144 possible names. The scope is clear enough to separate it from a signs-based sibling, since 'Birthdays alone are enough' implies the other tool needs pre-computed signs, but the sibling is never named so the distinction is inferred rather than stated.

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?

Gives real eligibility context ('Works for partners, friends and family', 'Both people must be 18 or over'), which tells the agent when the tool is applicable. However, it never states when to prefer the sibling tandem_name_for_signs (e.g. when signs are already known) or any case where this tool should not be used, so routing between the two remains implicit.

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