Skip to main content
Glama

A famous birth chart

get_famous_chart
Read-onlyIdempotent

Looks up the birth chart of a famous person Zodiacs publishes: Sun and Moon signs and the planets' signs for their birth date, a short introduction and a link to their page. It fits a question about a well-known person's chart or sign. It covers only the people Zodiacs publishes. For anyone else it says it has no chart (found: false) and returns none.

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": {
      "name": "<name>"
    },
    "name": "get_famous_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's name, such as Ada Lovelace.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, closed-world, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value beyond them by disclosing the not-found contract ('found: false' and no chart returned) and the shape of a successful result.

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?

Three short sentences, front-loaded with what it returns, then when to use it, then the failure mode. The 'covers only the people Zodiacs publishes' clause is restated slightly in the following sentence, a minor redundancy in an otherwise tight definition.

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 an output schema present, the description needn't document return fields, yet it still flags the found:false case, and rich annotations carry the safety profile. The only gap is name-matching behavior and any guidance on where to send users whose subject isn't published.

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?

There is a single parameter at 100% schema description coverage, so the baseline is 3. The description adds one meaningful constraint, that the name must belong to a Zodiacs-published person, but says nothing about matching behavior (exact vs. fuzzy, case sensitivity) that would help an agent retry or normalize input.

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 uses a specific verb and resource ('Looks up the birth chart of a famous person') and enumerates the payload (Sun and Moon signs, planetary signs, intro, page link). The 'Zodiacs publishes' scope implicitly separates it from a general natal-chart tool, but no sibling is named, so differentiation 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit use case ('fits a question about a well-known person's chart or sign') and an explicit when-not ('covers only the people Zodiacs publishes'; others return found: false and no data). It stops short of naming an alternative tool for non-famous people, which keeps it from a 5.

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.