Skip to main content
Glama

obsbot_preset_delete

Deletes an occupied preset slot (1, 2, or 3) on an OBSBOT Tiny 2 webcam and confirms removal by re-reading the preset list after writing.

Instructions

Delete preset slot 1|2|3. The slot must be occupied. 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": "obsbot_preset_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. Addedv0.6.2

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 the occupied-slot precondition and a post-write verification step, but it omits whether deletion is reversible, what error is returned if the slot is empty, and whether camera selection affects behavior.

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, front-loaded with the operation and valid slots, followed by the precondition and verification behavior. There is no wasted wording.

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?

For a simple two-parameter delete tool with no annotations or output schema, the description covers the core operation, slot range, precondition, and verification. It remains incomplete on the optional camera parameter, error behavior, and reversibility.

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

Parameters2/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 clarifies that slot accepts 1|2|3 and must be occupied, but the camera parameter is left completely unexplained, and there is no added meaning about slot identity beyond the schema's const constraints.

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?

The description states a specific verb and resource: delete a preset slot, with the valid slot range 1|2|3. It is distinguishable from sibling tools such as preset_save, preset_recall, and preset_list, although it does not explicitly name or contrast with them.

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

Usage Guidelines3/5

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

It gives a clear precondition that the slot must be occupied, which implies when deletion is valid. However, it does not say when to use this tool instead of alternatives or what to do if the slot is empty, and it gives no guidance on the optional camera parameter.

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