Skip to main content
Glama
Sign In
ygo-format

ygo-format

by andrewboe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

saved_decks

Read-only

List decks saved via finalize_deck, newest first, with name, format, saved_at, summary, .ydk path, and ydke URL; optionally filter by TCG Advanced or Genesys format.

Instructions

Decks saved with finalize_deck, newest first: name, format, saved_at, summary, .ydk path, ydke URL.

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

Input Schema

NameRequiredDescriptionDefault
formatNo

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?

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuine value on top: result ordering (newest first) and the exact field set returned. It does not cover pagination, result limits, or whether the format parameter narrows the list, so it stops short of 5.

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?

A single compact sentence, front-loaded with the resource and provenance, followed by the return fields. Nothing is padded and every clause carries information.

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?

With no output schema, the description usefully enumerates returned fields, and annotations cover the safety profile. However, it omits the semantics of the format filter, pagination/limit behavior, and whether an empty result is possible, leaving gaps for a listing tool.

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?

The single 'format' parameter has 0% schema description coverage and enum values (tcg_advanced, genesys) that are never explained. The description's mention of 'format' refers to an output field, not the input filter, so it does not compensate for the schema gap and could even mislead about what the parameter does.

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?

Identifies the exact resource ('decks saved with finalize_deck') and its ordering ('newest first'), letting an agent distinguish it from siblings like finalize_deck or search_cards. The verb (list/retrieve) is only implied rather than stated, which keeps it just 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?

Usage is only implied through the reference to finalize_deck as the producer of these records, so an agent can infer 'call this to see what you saved'. There is no explicit when-to-use/when-not statement or named alternative, and the role of the format parameter as a filter is not clarified.

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

Deploy Server

Other Tools