Skip to main content
Glama

Wall of Decks

list_decks

List the decks in the library with stage, amount, year, outcome and slide count.

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

Input Schema

NameRequiredDescriptionDefault
stageNo
outcomeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. It does disclose the returned fields (stage, amount, year, outcome, slide count), which is genuine behavioral value, but says nothing about pagination, result ordering, or the size of the library and how that affects the response.

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?

A single tight sentence with no padding and the resource front-loaded. It is concise, but the brevity comes partly at the cost of the missing filter and usage information rather than being purely efficient.

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

Completeness2/5

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

For a simple two-filter listing tool without an output schema, the description should at minimum explain the filters and the listing behavior. Neither is present, leaving the schema's enums undocumented and the response shape only partially implied.

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 description coverage is 0%, so the description must compensate for the two optional enum parameters (stage, outcome) — and it does not. Worse, the phrasing 'with stage, ... outcome' presents them as returned fields rather than as available filters, which could lead an agent to overlook the ability to narrow results.

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?

The description uses a specific verb ('List') and resource ('decks in the library') and even enumerates the returned fields, so an agent can tell it is a collection-read tool. It does not distinguish itself from siblings like get_deck or search_slides, but the core purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no statement of when to use this versus get_deck (single-deck retrieval) or search_slides (content search). Only a weak implication that this is the 'list everything' entry point, with no mention of whether the two filters are supported or how to combine them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources