Skip to main content
Glama

obsbot_preset_rename

Rename an occupied OBSBOT camera preset slot (1–3) and verify the new name by re-reading the slot list; names over 40 bytes are truncated.

Instructions

Rename preset slot 1|2|3. The slot must already be occupied. Names longer than 40 bytes are truncated to fit the wire frame. Verifies by re-reading the slot list after writing.

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_preset_rename"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
slotYes
cameraNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.6
    • removedInput schema / properties / slot / allOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "enum": [
      -      1,
      -      2,
      -      3
      -    ],
      -    "type": "number"
      -  }
      -]
    • addedInput schema / properties / slot / anyOf
      Added value: +[
      +  {
      +    "const": 1,
      +    "type": "number"
      +  },
      +  {
      +    "const": 2,
      +    "type": "number"
      +  },
      +  {
      +    "const": 3,
      +    "type": "number"
      +  }
      +]
  2. First observedv0.6.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does real work: it discloses silent data loss (>40 bytes truncated), a write precondition, and a post-write read-back verification. It still omits failure behavior, whether the camera parameter defaults to a device, and what the verification result is surfaced as.

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?

Three short sentences, zero filler, with the operation and its allowed slot values front-loaded and the caveats following in decreasing priority. Nothing repeats the tool name or the schema.

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 small mutation tool with no annotations, no output schema, and a simple flat schema, this covers the essentials an agent needs to call it safely: valid slots, the occupancy precondition, and the truncation hazard. The undocumented 'camera' parameter and absent error semantics are the remaining gaps.

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, and it adds real meaning for two of three parameters: slot (must already be occupied) and name (40-byte truncation). The third parameter, 'camera', is never mentioned, leaving an agent unable to tell whether it is required for multi-device setups or optional.

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?

The description names a specific verb and resource ('Rename preset slot') and immediately scopes it to slots 1|2|3, which lets an agent distinguish it from siblings like obsbot_preset_update or obsbot_preset_list without opening any 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?

It states a clear precondition ('The slot must already be occupied'), which is genuine when-to-use guidance for an agent deciding between renaming and saving. It does not explicitly name alternatives or say what to do if the slot is empty (save first? update?), so it falls short of full routing guidance.

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