Skip to main content
Glama
Sign In

asktian

by io.github.douglasgan
OverviewDiscussionsAdmin

asktian_name_analysis

Quick energetic profile of a name (姓名学 name-analysis). Useful when the user asks about someone's name, a baby name, a company name, or 'what kind of person is X' when no birthdate is available. Returns a one-line vibe + dominant element guess.

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": "asktian_name_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name to analyze. Can be in any script.
languageNoLanguage hint. Default 'auto'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided, so the description carries the full burden. It states the output is a 'one-line vibe + dominant element guess' and implies it's quick and non-invasive. However, it doesn't disclose methodology, limitations, or whether it's based on cultural systems (e.g., Chinese numerology).

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?

Two sentences front-load purpose and usage. Every sentence adds value. No redundant or filler content.

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 simple tool with 2 parameters, no output schema, and no annotations, the description covers purpose, usage scenarios, and output format. It is adequate, though additional context on cultural basis or limitations would improve completeness.

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%; both parameters have descriptions. The description adds that 'name' can be in any script, which is already in the schema, and does not add new meaning beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states it provides a 'quick energetic profile of a name' and lists specific use cases (baby names, company names). It differentiates from sibling tools by focusing on name analysis. However, 'energetic profile' is somewhat vague and could be more specific about what is returned (e.g., elements, traits).

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?

The description gives explicit scenarios for use (when user asks about someone's name, baby name, etc.) and notes it's useful when no birthdate is available. It does not explicitly state when not to use or mention alternatives among siblings, but the context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All asktian toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources