Skip to main content
Glama

obsbot_tail2_preset_rename

Rename Tail 2 camera preset slots 1–3 with custom names up to 40 characters; base64 encoding and decoding are handled automatically on the wire.

Instructions

Rename a Tail 2 preset slot (1–3). Names travel base64 on the wire; the tool encodes/decodes transparently (up to 40 chars).

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": {
      "slot": "<slot>",
      "name": "<name>"
    },
    "name": "obsbot_tail2_preset_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
slotYes
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.6
    • removedInput schema / properties / slot / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "maximum": 3,
      -    "minimum": 1,
      -    "type": "integer"
      -  }
      -]
    • addedInput schema / properties / slot / maximum
      Added value: +3
    • addedInput schema / properties / slot / minimum
      Added value: +1
    • addedInput schema / properties / slot / type
      Added value: +"integer"
  2. Addedv0.9.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that base64 encoding is handled transparently and that names are capped at 40 characters — real operational context — but says nothing about permissions, whether renaming an empty slot fails, or what happens to any prior name.

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 tightly packed sentences with zero filler; the operation and its scope come first, then the encoding caveat that would otherwise trip up a caller.

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

Completeness3/5

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

A mutation tool with no annotations and no output schema still leaves the `camera` parameter and error behavior unexplained, so the definition is workable but not complete for its complexity.

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 0%, so the description must compensate. It explains that `name` is plain text encoded for you and limited to 40 chars, but the `slot` explanation merely restates the schema's 1–3 bounds and the third parameter, `camera`, is never mentioned at all.

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?

Names a specific verb+resource ('Rename a Tail 2 preset slot') and even bounds the target to slots 1–3, so the agent knows exactly what is being modified. It does not, however, distinguish itself from the generic `obsbot_preset_rename` sibling, which appears to do the same thing for a different device family.

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

Usage Guidelines2/5

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

There is no statement of when to choose this over `obsbot_preset_rename` or `obsbot_preset_update`, nor any precondition such as the slot already holding a saved preset. The agent must infer the device-specific context from the name alone.

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