Skip to main content
Glama

obsbot_tail2_preset_delete

Delete a Tail 2 preset slot (1–3) to free it for reuse. Confirm by verifying the slot disappears from the preset list.

Instructions

Delete a Tail 2 preset slot (1–3), freeing it. Verified by the slot disappearing from the list.

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

Input Schema

NameRequiredDescriptionDefault
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.2/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 burden. It usefully discloses the state effect ('freeing it') and a verification method ('slot disappearing from the list'), which is real behavioral value. It does not say whether the deletion is irreversible, whether the slot becomes empty vs reset to defaults, or what errors occur for an out-of-range slot.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and scope, with no filler. Efficient, though the verification clause could carry more weight if paired with reversibility information.

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 mutation with no output schema, the description covers the core action and its observable effect. It is incomplete regarding the undocumented 'camera' parameter and the destructive/irreversible nature of the operation, which matter for an agent deciding to call a delete tool.

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 should compensate but does not. The 1–3 range merely restates the schema's min/max, and the 'camera' parameter is not mentioned at all, leaving its semantics (device selection? identifier format?) entirely undocumented in both schema and description.

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?

Specific verb+resource: 'Delete a Tail 2 preset slot (1–3)', with the effect ('freeing it') stated. It is distinguishable from the many sibling preset tools (save/recall/rename/list) by the delete verb, though it never names them explicitly.

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?

Usage is implied by the verb — use it when you want to remove a stored preset — but there is no explicit when-to-use/when-not guidance, no mention of alternatives (e.g., overwriting a slot via obsbot_tail2_preset_save instead of deleting), and no statement about whether the removed preset is recoverable.

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