Skip to main content
Glama
Sign In

concordance

by com.narrowhighway
OverviewDiscussionsAdmin

deck_open

[KEEP · internal] Open a deck to its frontloaded hand — the cards that situation calls for, in order, with NO query needed. Give the deck id (from decks). Ideal for anticipating need: open 'water-safe', 'first-aid-far', 'grow-food', 'be-not-afraid', etc., and get the hand ready to read.

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": {
      "id": "<id>"
    },
    "name": "deck_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It conveys that results are ordered and query-free, but says nothing about whether the call is read-only, permission/auth needs, error behavior, or what the unmentioned `limit` does — thin for a tool with zero structured behavioral coverage.

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?

Reasonably short and the purpose is front-loaded after the '[KEEP · internal]' marker, with examples placed last. The metaphor-heavy phrasing and marker consume some space without adding operational meaning, but there is no real padding.

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?

There is no output schema or annotations, so the description must be self-sufficient. It does explain the id source and that cards come back in order, but omits `limit` semantics and error/edge behavior, leaving gaps an agent would need before invoking confidently.

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 both parameters. It explains only `id` (from `decks`); the optional `limit` parameter is never mentioned, leaving the agent without guidance on its meaning despite a schema that offers no description either.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb+resource (open a deck) is present and it distinguishes itself from the sibling `decks` (which it cites as the source of `id`). But the core output is described only in opaque internal jargon — 'frontloaded hand — the cards that situation calls for' — which an agent cannot fully decode without prior ecosystem knowledge.

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?

It offers example deck names ('water-safe', 'first-aid-far') and a use case ('ideal for anticipating need'), which implies when to reach for it, and notes 'NO query needed'. However it names no alternative or exclusion, so an agent cannot tell when another tool (e.g. `cards_browse`, `ask`) would be preferred.

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

All concordance toolsInspect
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