Skip to main content
Glama

personal_report

Complete personal report in one call: today's reading with phrases and tips, chakra of the day with practice, best days of the next 30 days for 8 activities, critical days, personal archetype, optional couple compatibility. Price: $0.05 USDC per call (x402).

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

Input Schema

NameRequiredDescriptionDefault
dateNoDay (default: today UTC)
langNoLanguage of the core texts (default it)
birthYesBirth date YYYY-MM-DD
partnerNoOptional partner birth date for compatibility

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations at all, the description still discloses two behaviorally important facts not present in structured fields: the tool is a paid call ($0.05 USDC via x402) and it bundles a fixed set of report sections rather than returning arbitrary data. It does not describe failure modes, payment rejection behavior, or whether the underlying text generation is cached/deterministic.

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?

A single front-loaded sentence lists the deliverables first and the cost last, with no filler. The dense comma list is justified by the breadth of the payload, though splitting the pricing clause into its own sentence would improve scannability.

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 composite tool with no output schema and no annotations, the description compensates by enumerating exactly which sections come back, which is the key thing an agent needs to decide whether to spend a paid call. It leaves some ambiguity about the response structure (nested sections, relative sizes) and default behaviors when optional params are omitted.

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%, so every parameter already has its own description; the description adds only the note that partner drives 'couple compatibility' and that the report spans a fixed 30-day / 8-activity window (which has no corresponding parameter). Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific resource (personal report) and enumerates its contents — daily reading, chakra of the day, best days for 8 activities over 30 days, critical days, archetype, optional couple compatibility — which makes its composite, one-shot nature clear against the granular siblings. It stops short of naming the sibling tools it replaces, so differentiation is inferable rather than explicit.

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?

The phrase 'in one call' implies this is the aggregated alternative to calling biorhythm_day, chakra_of_the_day, biorhythm_best_days and similar tools separately, and 'optional couple compatibility' hints at when partner matters. However, there is no explicit when-to-use / when-not-to-use guidance or a named alternative, leaving the routing decision to inference.

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