Skip to main content
Glama

add_ruling

Add a curated One Piece Card Game ruling and immediately index it in FTS5, with source-based authority for searchable knowledge base curation.

Instructions

Add a curated OPTCG ruling (always enters with reviewed=False) and index its chunk immediately in FTS5. Authority is derived from source ('official_faq'/'errata'=2, 'judge'=3, 'community'=4). Optional judge_tier ('tier_0' | 'tier_2' | 'tier_1', precedence tier_0 > tier_2 > tier_1) is valid for source='judge'. Never pass personal names, @handles, or Discord user IDs.

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": {
      "question": "<question>",
      "answer": "<answer>",
      "source": "<source>"
    },
    "name": "add_ruling"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo
dateNo
answerYes
sourceYes
raw_refNo
card_idsNo
questionYes
rule_refsNo
judge_tierNo
rules_versionNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/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 burden and does substantial work: it discloses the forced reviewed=False state, immediate FTS5 indexing, how authority is derived from source, and the precedence ordering for judge_tier. It omits what happens on duplicate questions, whether entries can be edited afterward, and any failure modes, which keeps it short of a 5.

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-loads the action and its side effects, then layers the derivation rules and constraints in descending importance. Dense but every clause carries information; the only mild redundancy is restating the source-to-authority mapping twice implicitly through judge_tier's restriction.

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?

For an unannotated write tool with an output schema present (so return values needn't be explained), the description covers the key business logic but leaves too many inputs undefined and never positions the tool against mark_ruling. An agent could call it, but would be guessing on card_ids, rule_refs, raw_ref, and rules_version.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% across 10 parameters, so the description must compensate, and it only documents two of them: it enumerates the source values with their authority weights and spells out judge_tier's allowed values, precedence, and source restriction. The remaining eight parameters (url, date, raw_ref, card_ids, rule_refs, rules_version, question, answer) receive no semantics at all, leaving most of the surface undocumented.

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 ('Add') and a specific resource ('curated OPTCG ruling'), plus two consequences of the call: it always enters with reviewed=False and is indexed into FTS5 immediately. It does not name or differentiate itself from the closest sibling, mark_ruling, so an agent must infer the boundary between adding and marking.

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?

Provides a real applicability constraint ('judge_tier ... is valid for source=judge') and a hard prohibition ('Never pass personal names, @handles, or Discord user IDs'), which is valuable when-to/when-not guidance. However, it never says when to choose this over mark_ruling or how it relates to list_unreviewed_rulings, leaving the main sibling-selection decision implied.

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