Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Remove Profile

obs-remove-profile
DestructiveIdempotent

Delete an OBS profile, automatically switching to another if the current one is removed.

Instructions

Removes a profile. If the current profile is chosen, it will change to a different profile first

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": {
      "profileName": "<profileName>"
    },
    "name": "obs-remove-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNameYesName of the profile to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, so the safety profile is known. The description adds value by disclosing that selecting the current profile triggers an automatic switch to another profile first, a non-obvious behavior. This extra context goes beyond the annotations and is essential for safe invocation.

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?

The description is a single, compact sentence that packs the core action and a crucial edge case. There is zero filler, and every word earns its place. It is optimally concise and front-loaded.

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?

For a simple one-parameter destructive tool with clear annotations, the description covers the essential action, the special behavior when removing the current profile, and does not need to elaborate on return values (no output schema). It is complete for the tool's 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?

The schema description fully covers the only parameter 'profileName' with 'Name of the profile to remove'. The tool description does not add additional meaning or constraints beyond that. Given the 100% schema coverage, the baseline score of 3 is appropriate; the description contributes nothing new param-wise.

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 clearly states 'Removes a profile', using a specific verb and resource. It distinguishes from sibling profile tools like obs-create-profile and obs-set-current-profile by specifying the removal intent. The added note about switching profiles if the current one is selected further clarifies the exact scope.

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?

The description implies usage for removing profiles but does not explicitly compare with alternatives or state when not to use. The side-effect note about current profiles provides some contextual guidance, but there is no clear 'use this instead of X' or exclusion criteria. This earns a middle score.

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