Skip to main content
Glama

show_status_card

Displays splatmaker engine and job-queue status in a rich Prefab card, showing engine state, job counts by status, and backend port for monitoring.

Instructions

Show splatmaker engine + job-queue status as a rich Prefab card.

Return Format

A ToolResult with plain-text content (same numbers as the card) and structured_content carrying the PrefabApp view for Prefab-capable hosts.

Examples

show_status_card() -> card with engine state, job counts by status, backend port.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return shape, plain-text content mirroring the card numbers plus structured_content holding the PrefabApp view, which is genuinely useful. It says nothing about whether the call is read-only, whether it has side effects on the queue, or any latency or rate constraints.

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?

The content is short and front-loaded, with the purpose in the first sentence. The '## Return Format' and '## Examples' headers are heavier structure than a one-sentence tool needs, but every line still carries information.

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 no-argument status tool with an output schema, this covers purpose, return shape, and a concrete example, which is close to everything an agent needs. The one real gap is that it does not clarify how it relates to the near-duplicate splat_engine_status.

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 add and the baseline is a 4. The example call show_status_card() reinforces that no arguments are expected.

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 gives a specific verb and resource: show splatmaker engine and job-queue status, presented as a rich Prefab card. That presentation detail distinguishes it from a plain status reader like splat_engine_status, but the relationship is only implicit rather than stated.

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 implied by the word 'card' and the mention of Prefab-capable hosts, so an agent can infer this is the display-oriented variant. There is no explicit when-to-use or when-not guidance, and no named alternative such as splat_engine_status, so the choice between siblings is left to inference.

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