Skip to main content
Glama
Sign In
PikoReels MCP

PikoReels MCP

by Honey2339
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Keep or skip a Rush card

resolve_rush_item

Resolve each card from get_rush_feed by keeping it to create a reel or skipping it to discard it and release its daily allowance hold.

Instructions

Decide a card that has been dealt — keep it, which turns it into a reel, or skip it, which returns its hold on the daily allowance. Every card from get_rush_feed should end up here.

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": {
      "itemId": "<itemId>",
      "decision": "<decision>"
    },
    "name": "resolve_rush_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesCard id from get_rush_feed.
decisionYes'keep' makes a reel from it; 'skip' discards it and frees the hold.
workspaceIdNoWorkspace to act in. Defaults to the active one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare the mutation/safety profile (readOnlyHint=false, destructiveHint=false), so the bar is lower, yet the description adds real domain behavior: 'keep' materializes a new artifact (a reel), and 'skip' releases a hold against the daily allowance — a quota side effect the annotations do not convey. It does not state whether a decision is reversible or what happens on a duplicate/already-resolved card, so it is not fully transparent.

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?

Two sentences, no filler, and the core decision semantics are front-loaded before the workflow note. Every clause carries information an agent needs.

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 3-parameter mutation tool with no output schema, the description covers the action, both outcomes, and the upstream feed relationship; the workspace default is handled by the schema. Missing only edge behavior (idempotency/re-resolution, error outcomes), which keeps it from a 5.

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

Parameters3/5

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

Schema description coverage is 100%: itemId, decision (with enum), and workspaceId are all documented in the schema, including the keep/skip semantics. The description only restates the same keep/skip behavior in prose, adding no format or fallback detail beyond the schema, so the baseline 3 applies.

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

Purpose5/5

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

States a concrete verb+resource ('Decide a card that has been dealt') and names both outcome branches with their consequences ('keep' → reel, 'skip' → frees the hold). It also explicitly ties itself to the sibling get_rush_feed ('Every card from get_rush_feed should end up here'), so an agent can distinguish it without opening the schema.

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

Usage Guidelines4/5

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

The second sentence gives a clear usage condition: every card returned by get_rush_feed is expected to pass through this tool, which effectively defines the when and the upstream prerequisite. It stops short of stating when NOT to call it (e.g. cards already resolved, or whether a decision is final and re-decidable), so it is clear context without exclusions.

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