Shootika

Get shoot

get_shoot

Read-only

Returns one shoot (frame), waiting up to 8 seconds for it to finish (one wait at a time per connection; a second call answers at once). A ready frame comes with a small preview image and its full-size url. If it is still queued or processing when the wait ends, call get_shoot again with the same frame_id. A failed frame says why; its frame was refunded.

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": {
      "frame_id": "<frame_id>"
    },
    "name": "get_shoot"
  }
}

Input Schema

Name	Required	Description	Default
`frame_id`	Yes	The frame id from start_shoot or list_shoots.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnlyHint annotations: the 8-second wait window, connection-level concurrency semantics, what a ready frame contains (preview image plus full-size URL), the retry expectation, and that a failed frame reports a reason and is refunded. None of this is inferable from annotations or schema.

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?

Four tight sentences, front-loaded with what is returned, then wait semantics, then the retry rule and failure behavior. Every sentence carries information an agent needs to drive the polling loop.

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

Completeness5/5

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

No output schema exists, so the description must describe returns and it does: preview image, full-size URL, failure reason plus refund. Combined with the documented wait and retry behavior, an agent has everything needed to call and re-call this tool correctly.

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 coverage is 100% and the frame_id description already points to start_shoot or list_shoots as its source. The prose reinforces reuse ("call get_shoot again with the same frame_id") but adds no format or constraint 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 specific verb and resource ("Returns one shoot (frame)") and disambiguates the naming by equating shoot with frame. The singular "one shoot" plus the required frame_id clearly separates it from the sibling list_shoots.

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?

Gives explicit operational guidance: it waits up to 8 seconds, only one wait per connection, a second call answers immediately, and if still queued/processing you should call get_shoot again with the same frame_id. It does not discuss when to prefer list_shoots or other siblings, but the polling contract is clear.

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

All Shootika tools Inspect

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

Need Help?