Skip to main content
Glama

Organize with AI (OwAI)

Manage an automatic or manual group

manage_group
Destructive

Create, rename, update dates, delete, change image membership, or edit text keywords using the app's automatic-fill rules. add_keyword accepts keyword text and OwAI generates the same search embedding used by the app; never provide a vector. remove_keyword uses a keyword_id returned by inspect_library. For update_dates supply both start_timestamp and end_timestamp; null removes a bound. Local sources execute on the owning device; OneDrive sources execute on the server without a desktop. To create, source_name identifies the folder directly.

Input Schema

NameRequiredDescriptionDefault
nameNo
keywordNo
group_idNo
asset_idsNo
device_idNo
operationYes
source_idNo
keyword_idNo
source_nameNo
end_timestampNo
confirm_deleteNo
idempotency_keyNo
start_timestampNo

Output Schema

NameRequiredDescriptionDefault
commandYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / allOf
      Added value: +[
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "create"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "oneOf": [
      +        {
      +          "not": {
      +            "required": [
      +              "source_name"
      +            ]
      +          },
      +          "required": [
      +            "source_id"
      +          ]
      +        },
      +        {
      +          "not": {
      +            "required": [
      +              "source_id"
      +            ]
      +          },
      +          "required": [
      +            "source_name"
      +          ]
      +        }
      +      ],
      +      "required": [
      +        "name"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "rename"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "group_id",
      +        "name"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "update_dates"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "group_id",
      +        "start_timestamp",
      +        "end_timestamp"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "delete"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "properties": {
      +        "confirm_delete": {
      +          "const": true
      +        }
      +      },
      +      "required": [
      +        "group_id",
      +        "confirm_delete"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "enum": [
      +            "add_assets",
      +            "remove_assets"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "group_id",
      +        "asset_ids"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "add_keyword"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "group_id",
      +        "keyword"
      +      ]
      +    }
      +  },
      +  {
      +    "if": {
      +      "properties": {
      +        "operation": {
      +          "const": "remove_keyword"
      +        }
      +      },
      +      "required": [
      +        "operation"
      +      ]
      +    },
      +    "then": {
      +      "required": [
      +        "group_id",
      +        "keyword_id"
      +      ]
      +    }
      +  }
      +]
    • addedInput schema / properties / asset_ids / minItems
      Added value: +1
    • addedInput schema / properties / keyword
      Added value: +{
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / keyword_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "minLength": 1,
      +      "type": "string"
      +    },
      +    {
      +      "exclusiveMinimum": 0,
      +      "maximum": 9007199254740991,
      +      "type": "integer"
      +    }
      +  ]
      +}
    • changedInput schema / properties / operation / enum
      Previous value: -[
      -  "create",
      -  "rename",
      -  "update_dates",
      -  "delete",
      -  "add_assets",
      -  "remove_assets"
      -]New value: +[
      +  "create",
      +  "rename",
      +  "update_dates",
      +  "delete",
      +  "add_assets",
      +  "remove_assets",
      +  "add_keyword",
      +  "remove_keyword"
      +]
    • 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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered and the description is not required to restate it. It adds real behavioral context the annotations do not: local sources execute on the owning device while OneDrive sources execute server-side without a desktop, and null timestamps remove a bound rather than erroring. It still never states that delete is irreversible or how confirm_delete gates the action.

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?

Front-loaded with the operation list, then compact per-operation notes with no filler sentences. The block of caveats is dense but each sentence carries a distinct constraint. Slightly run-on in the middle where execution-location and create-routing facts are stacked without grouping.

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?

An output schema exists so return values need not be described, which relieves some burden. For a 13-parameter, 0%-coverage, destructive multi-operation tool, however, the description leaves gaps: idempotency and device targeting are unexplained, and the delete confirmation flow is only inferable from the schema's conditional.

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 0% across 13 parameters, so the description carries the entire burden of parameter meaning. It usefully clarifies keyword (text, embedding generated by OwAI), keyword_id (retrieved via inspect_library), both timestamps (null removes a bound), and the create-time source_name/source_id choice. It says nothing about device_id, idempotency_key, or the semantics/limits of asset_ids, leaving several high-impact parameters undocumented.

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 first sentence enumerates the eight concrete operations (create, rename, update dates, delete, change image membership, edit text keywords) against a single named resource, 'group', so an agent knows exactly what class of action this tool performs. The combination of membership editing plus automatic-fill keyword rules makes it specific enough to distinguish from the other manage_* siblings.

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

Usage Guidelines4/5

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

The description routes per-operation: add_keyword takes keyword text (never a vector), remove_keyword needs a keyword_id from inspect_library, update_dates needs both bounds, and create is driven by source_name. It names a sibling tool as the source for keyword_id, which is genuine cross-tool guidance. It does not, however, state when to prefer this tool over manage_collection or manage_person, nor any preconditions for the delete path.

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