Skip to main content
Glama
Ancient Echoes MCP

Ancient Echoes MCP

Family Relations Context

bazi.prepare_family_relations_context
Read-only

Prepares a BaZi family-relations evidence context from a user’s own record or profile, returning palace, ten-god, and multi-school six-kin mappings without inferring family facts.

Instructions

为当前用户自己的八字记录或本人资料准备家庭关系证据上下文:返回四柱宫位、天干与藏干十神、多流派六亲映射及不可用边界;不推断父母强势方、亲属人数或性别、支持/消耗、家庭事实或隐式岁运。

Input Schema

NameRequiredDescriptionDefault
record_idNo
use_profileNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.9/5.0
Behavior4/5

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

With readOnlyHint already declared, the description still adds real value by disclosing the evidence categories returned and by drawing explicit negative boundaries (no parent-dominance, headcount, gender, support/drain, family facts, or implicit suiyun inference). What remains unstated is the shape/size of the returned context, which is a minor gap for a read-only tool.

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?

One dense sentence, front-loaded with the purpose and tail-loaded with exclusions; nothing is redundant. The enumeration of both returned data and negative boundaries is long but each clause carries distinct information.

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?

No output schema exists, so the description must characterize the return, and it does so at the level of concrete evidence categories plus explicit non-inferences. Combined with read-only annotations this is close to complete; only error/empty-case behavior is untouched.

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 description coverage is 0%, so the description carries the burden. It conveys that the two mutually exclusive inputs are 'the user's own bazi record' versus 'own profile', which disambiguates the oneOf intent, but it never clarifies that record_id is an integer id or that use_profile must be set true, and it does not say what happens if neither is supplied.

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 concrete verb+resource: 'prepare family relations evidence context' for a bazi record, and enumerates the payload (four-pillar palaces, stem/hidden-stem ten gods, multi-school six-kin mappings). It implicitly separates itself from bazi.prepare_naming_context by domain, but never names a sibling, so it stops short of a 5.

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?

Explicitly scopes invocation to the user's own bazi record or own profile, which matches the schema's oneOf exactly, and gives a substantial list of questions this tool will not answer. It does not name an alternative tool for those out-of-scope questions, 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.