Skip to main content
Glama

Have her take a new photo or video right now

shoot

Requests a new photo or video from your 37Soul AI character when the user asks for a picture of her right now; call only on request, as it spends credits and is rate-limited.

Instructions

Ask her to shoot something NEW this moment — not one of the pictures she already has (those are in whoami's photos / videos). Use it when the person asks for a picture of her right now. It spends the account's credits and is capped per hour, so do not call it on your own initiative and never retry a refusal in a loop. photo comes back immediately with a URL; video takes about 95 seconds (measured) and arrives later in read_chat_history.

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

Input Schema

NameRequiredDescriptionDefault
kindNo`photo` is instant. `video` is asynchronous and costs much more — only when they asked for a video.photo
host_idNoThe host's id. Optional when SOUL37_HOST_ID is set — then it defaults to the bound host.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.15.3
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / host_id / maximum
      Added value: +9007199254740991
  2. Addedv0.11.0

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses credit spend, an hourly cap, refusal non-retryability, per-kind latency (instant vs ~95 measured seconds), and where the asynchronous video result surfaces (`read_chat_history`). That is unusually rich behavioral context for an unannotated tool.

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?

Front-loaded with the core action and the NEW-this-moment distinction, then cost/rate constraints, then per-kind return behavior. Dense but every clause carries operational information; nothing is filler.

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, yet the description explains the return path for both kinds (URL for photo, deferred delivery for video). For a 2-parameter, zero-required-parameter tool, an agent has everything needed to decide and call correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: that `video` arrives later via `read_chat_history` rather than in the response, which changes how an agent should sequence calls. The `host_id` default behavior is left entirely to the schema.

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 ('shoot something NEW this moment') and immediately disambiguates from existing media stored in whoami's `photos` / `videos`, which is the exact confusion an agent would have against the sibling `read_host_photos`.

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

Usage Guidelines5/5

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

Explicit trigger ('when the person asks for a picture of her right now'), explicit prohibition ('do not call it on your own initiative'), an anti-pattern ('never retry a refusal in a loop'), and points to the alternative source for existing media. Nothing 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.