Skip to main content
Glama

ai_modeling_gallery_uncollect

Removes a gallery model from your collection by ID, enabling agents to clean up saved Studio assets without manual account changes.

Instructions

Remove a gallery model from your collection.

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": {
      "id": "<id>"
    },
    "name": "ai_modeling_gallery_uncollect"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, and the description usefully reinforces that this removes an entry from the user's collection rather than deleting the underlying model — consistent with the annotations. It says nothing about idempotency, behavior when the id is not in the collection, or whether auth is required, so it adds modest value over the structured fields.

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?

One short, front-loaded sentence with no filler. It is efficient, but the brevity edges toward under-specification rather than tightness.

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 one-parameter tool with annotations covering its safety profile and no output schema, the description is minimally adequate. It leaves open what the return value is, whether the call is idempotent, and what happens on an id that was never collected — gaps an agent may care about for a state-changing call.

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?

The single required parameter `id` has 0% schema description coverage and the description never mentions it, so the agent gets no statement of what the id refers to (a gallery model id) or where to obtain one. Only the loosest inference from "a gallery model" ties the parameter to its meaning.

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?

"Remove a gallery model from your collection" pairs a specific verb with a specific resource and scopes it to the caller's collection, which implicitly distinguishes it from browse/like/tag siblings that operate on the public gallery. It stops short of naming ai_modeling_gallery_collect as its inverse, but the operation itself is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, no mention of the counterpart collect tool, and no prerequisites (e.g., that the model must currently be collected). Usage is only inferable from the phrase "from your collection."

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