Skip to main content
Glama

search

Retrieve One Piece Card Game rules, card data, FAQs, and judge rulings via hybrid keyword/vector matching; filter by authority level and exclude superseded rulings by default.

Instructions

Hybrid search across OPTCG Comprehensive Rules, cards, FAQs, and judge rulings using exact-match OPTCG token detection (card IDs, rule numbers, [Keywords]), FTS5 BM25, and local sqlite-vec embeddings fused with RRF and authority tie-breaking. min_authority filters authority <= N (1=rules only, 2=rules+official_faq/errata, 3=+judge, 4=all). Superseded rulings are excluded unless include_superseded=True.

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

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
doc_typesNo
min_authorityNo
include_supersededNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose non-obvious defaults: superseded rulings are excluded unless include_superseded=True, authority tie-breaking is applied, and results come from fused exact-match/BM25/vector sources. That is real behavioral context an agent could not infer. It omits result-count defaults and any cost/latency notes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and resource list, which is good. However, implementation jargon (FTS5 BM25, sqlite-vec, RRF fusion) consumes roughly half the text without helping an agent decide or invoke; the min_authority parenthetical is the genuinely load-bearing part.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return format need not be explained. But for a 5-parameter tool with 0% schema documentation, the description should have named the accepted doc_types values and what k controls; without them the definition is not quite sufficient to call the tool correctly in non-default cases.

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 0%, so the description must compensate. It does this well for min_authority (spelling out each level 1-4) and adequately for include_superseded, but leaves k (result count, default 8) and doc_types (valid values) entirely undocumented in both schema and description – a real gap for a filter parameter with no enum.

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 specific verb ('Hybrid search') and enumerates the corpora it spans: Comprehensive Rules, cards, FAQs, and judge rulings. That is enough for an agent to tell it apart from narrow siblings like search_cards or get_rule, though it never names those siblings directly.

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?

Usage is implied by the corpus list and the min_authority dial, but there is no explicit 'use this instead of X when...' guidance and no statement of when this tool is the wrong choice versus search_cards or get_card_rulings. The authority-level semantics are the closest thing to selection guidance.

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