MysticAPI

signature_lookup

Ratified Kairos' Council figure-signature canon (cross-product canon, ratified 2026-07-19): 9 signature templates and 35 carrier figures with template assignment, one-line historical argument, parameterization, and primary forge. Input: figure (name or slug) for one figure, or template (T1–T9 or name) for a template and all its carriers. Static canon data — deterministic. Costs 1 call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "signature_lookup"
  }
}

Input Schema

Name	Required	Description	Default
`figure`	No	Figure name or slug, e.g. "Joan of Arc" or "joan-of-arc". Returns that figure's canon record.
`template`	No	Signature template id (T1–T9) or name (e.g. "Last Testament"). Returns the template and every ratified carrier.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 11, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations the description carries the full burden, and it usefully discloses determinism ('static canon data — deterministic') and cost ('Costs 1 call'). It does not say how the two optional parameters interact, what happens on an unmatched name, or how errors surface.

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?

Front-loaded and dense: canon scope first, then input modes, then behavioral notes. The 'Ratified Kairos' Council ... ratified 2026-07-19' phrasing is slightly redundant world-building, but nearly every clause carries 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?

With no output schema, the description helpfully enumerates the return payload (template assignment, one-line historical argument, parameterization, primary forge). The remaining gap is a missing statement on the zero-required-parameter case.

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 100%, so the schema already documents both parameters and their examples. The description restates the same figure/template semantics and formats (T1–T9) without adding meaning beyond the schema, matching the baseline 3.

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 the resource precisely (a ratified canon of 9 signature templates and 35 carrier figures) and what a lookup returns for each input mode. It does not name a sibling or explain how it differs from the astrology/numerology tools it sits beside, 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 Guidelines3/5

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

The two input modes imply usage (figure for one record, template for a template plus carriers), but there is no explicit when-to-use, no note on what happens with neither/both parameters, and no routing versus the sibling tools. Usage is inferable rather than stated.

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

All MysticAPI tools Inspect

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

Need Help?