Skip to main content
Glama

Overlay: Together

Tandem name for a composite Sun and Moon

tandem_name_for_signs
Read-onlyIdempotent

Given the sign of a composite Sun and a composite Moon (the Sun and Moon of the chart two people make together, not either person's own signs), returns the pair's Tandem name and its one-line description. Takes no personal details.

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": {
      "sun": "<sun>",
      "moon": "<moon>"
    },
    "name": "tandem_name_for_signs"
  }
}

Input Schema

NameRequiredDescriptionDefault
sunYesThe composite Sun's sign, such as Aquarius.
moonYesThe composite Moon's sign, such as Taurus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world; the description adds that the output is a name plus a one-line description and that no personal data is consumed, which is real behavioral context. For a pure lookup table there is little else to disclose, so this is near-complete.

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 sentence with the input definition front-loaded, the disambiguating clause in a tight parenthetical, and the return value plus data-privacy note trailing. No filler and nothing repeated from the schema.

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?

For a two-enum-parameter lookup with no output schema, the description covers inputs, the meaning of 'composite', the return shape, and the fact that no personal details are needed. Nothing an agent would need to call it correctly is missing.

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% with enums and per-parameter descriptions, so baseline would be 3. The description earns above baseline by defining what 'composite' actually means and warning that these are not either individual's signs, resolving the main ambiguity in the schema's own parameter wording.

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+resource: takes a composite Sun sign and composite Moon sign and returns the pair's Tandem name plus a one-line description. The parenthetical explicitly disambiguates composite signs from either person's own signs, which is exactly the distinction an agent would need against a personal-sign lookup sibling.

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?

Provides clear context for use: only composite (relationship-chart) Sun and Moon signs, and explicitly notes no personal details are required, so an agent knows not to gather birth data first. It does not name the sibling tool as the alternative for personal signs, stopping short of explicit when-not 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.

Resources