Skip to main content
Glama

decken_capabilities

Inspect gateway capabilities, supported VLM models, token pricing, batch limits, and native OpenXML primitives before compiling slide designs into editable PowerPoint files.

Instructions

Inspect Decken gateway capabilities, supported VLM models, token pricing, batch limits (up to 24 slides/deck), and native OpenXML primitives.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral burden, and 'Inspect' only weakly signals a read-only, side-effect-free operation. It usefully discloses domain constraints (batch limits up to 24 slides/deck), but says nothing about whether results are cached or free to call, or how the capability data is structured.

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 front-loaded sentence with no filler; every listed item (models, pricing, batch limits, OpenXML primitives) is informative. It is a dense enumeration rather than a structured list, but it stays readable and short.

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

Completeness4/5

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

For a zero-parameter, read-only discovery tool with no output schema, the description adequately enumerates the categories of information returned, which is what an agent needs to decide to call it. Minor gap: it does not indicate the response shape or whether pricing units are per-token or per-request.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline applies. The description correctly requires no argument discussion and focuses entirely on what the call surfaces.

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?

A specific verb ('Inspect') plus a specific resource ('Decken gateway capabilities') with an enumeration of the concrete facts exposed: VLM models, token pricing, batch limits, and OpenXML primitives. That content implicitly separates it from the generative siblings (decken_generate, decken_reconstruct_deck), though no sibling is named explicitly.

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: an agent can infer this is the discovery/metadata call to make before generating decks or checking pricing. There is no explicit statement of when to prefer it over siblings such as decken_compare_models, and no stated prerequisites or exclusions.

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