Skip to main content
Glama
Sign In
OBS MCP

OBS MCP

by Tom-R-Main
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Hybrid

Get Scene Item Transform

obs-get-scene-item-transform
Read-onlyIdempotent

Retrieve the position, rotation, scale, or crop values of any OBS scene item to verify or sync its transform state.

Instructions

Get the position, rotation, scale, or crop of a scene item

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": {
      "sceneItemId": "<sceneItemId>"
    },
    "name": "obs-get-scene-item-transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneNameNoName of the scene containing the item
sceneUuidNoUUID of the scene containing the item
canvasUuidNoUUID of the canvas containing the scene
sceneItemIdYesThe ID of the scene item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, informing the agent this is a safe read operation. The description adds only that it retrieves transform components, providing minimal extra behavioral context. It does not describe the return format (e.g., whether it returns a single object with all properties) or any potential errors, but the annotations cover the key safety aspects, so the description meets a baseline level.

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, concise sentence with zero redundancy. It front-loads the action and target, making it immediately understandable. No unnecessary words or details are included, achieving perfect conciseness.

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?

Given the tool is a read-only getter with fully documented parameters and safe-operation annotations, the description is largely sufficient. The only gap is that it doesn't explicitly state that it returns all four transform properties together, which could be inferred but would help clarify the return value. Since no output schema exists, a brief note on the return structure would be beneficial but is not critical.

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 100%, meaning each parameter has a clear description in the input schema. The tool description adds no additional parameter semantics—it doesn't clarify preferred identifiers or relationships between sceneName, sceneUuid, and canvasUuid. Since the schema already handles parameter documentation, a score of 3 is the appropriate baseline.

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 the tool's purpose: retrieving position, rotation, scale, or crop of a scene item. It uses a specific verb ('get') and identifies the resource ('scene item transform'), distinguishing it from other scene-item getters (e.g., enabled, index, locked) which handle different properties. The phrase 'or' might imply a choice, but it broadly covers the transform components, making the intent unambiguous.

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 provides no explicit when-to-use or alternative guidance. However, the purpose is self-evident: it's a read operation for transform data, and no competing getter exists for the same property. The absence of exclusions or mentions of when not to use it is acceptable given the simplicity, but it could be improved by noting that scene identifier parameters are optional or that a scene must be specified in practice.

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