Skip to main content
Glama

Organize with AI (OwAI)

Open media on this computer

open_media

Launch a viewer for one asset on this connection's explicitly bound local computer. Requires current locate_media availability=local_device and an online app on that computer; OwAI rechecks access and rejects another device's local files. OneDrive assets open from the synced cloud replica on the bound computer. This is a user-visible side effect, not a content download. read_media returns content without launching windows.

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": {
      "asset_id": "<asset_id>"
    },
    "name": "open_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idYes
idempotency_keyNo

Output Schema

NameRequiredDescriptionDefault
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedOutput schema / properties / command / properties / attempt / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / command / properties / attempt / minimum
      Added value: +0
    • changedOutput schema / properties / command / properties / attempt / type
      Previous value: -"number"New value: +"integer"
    • addedOutput schema / properties / command / properties / claimed_at / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / command / properties / claimed_at / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / command / properties / completed_at / anyOf
      Added value: +[
      +  {
      +    "maximum": 9007199254740991,
      +    "minimum": 0,
      +    "type": "integer"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / command / properties / completed_at / type
      Removed value: -[
      -  "number",
      -  "null"
      -]
    • addedOutput schema / properties / command / properties / requested_at / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / command / properties / requested_at / minimum
      Added value: +0
    • changedOutput schema / properties / command / properties / requested_at / type
      Previous value: -"number"New value: +"integer"
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this is a user-visible side effect rather than a content download. It also explains access revalidation, rejection of another device's local files, and OneDrive opening from the synced replica.

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 front-loaded with the core action and then adds necessary constraints and the read_media distinction. Every sentence contributes useful information without redundant phrasing.

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?

The description covers the main behavioral and access preconditions well, and an output schema exists so return values need not be explained. The remaining gap is the unexplained idempotency_key parameter, which is relevant for invocation but optional.

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 needs to carry parameter meaning, but it only implicitly refers to 'one asset' for asset_id. The idempotency_key parameter is not mentioned or explained at all, leaving a significant gap for an action tool.

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 states a specific verb and resource: launch a viewer for one asset on the explicitly bound local computer. It also distinguishes the tool from the sibling read_media by noting that read_media returns content without launching windows.

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

Usage Guidelines5/5

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

It gives explicit preconditions: locate_media must currently report availability=local_device, an app must be online on that computer, and access is rechecked. It also names the alternative read_media for content retrieval, making when-to-use and when-not-to-use clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources