Skip to main content
Glama
Mipiti

Mipiti MCP Server

by Mipiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Remove Model From Group

remove_model_from_group

Remove a model from a tag without deleting it. The model's selected frameworks remain unchanged.

Instructions

Remove a model from a tag. Mutating; the model itself is not deleted.

The frameworks the tag propagated to the model stay selected on it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesthe tag.
model_idYesthe model to remove.
server_versionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.85.0
    • addedInput schema / properties / group_id
      Added value: +{
+  "description": "the tag.",
+  "type": "string"
+}
    • removedInput schema / properties / tag_id
      Removed value: -{
-  "description": "the tag.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "server_version",
-  "tag_id",
-  "model_id"
-]New value: +[
+  "server_version",
+  "group_id",
+  "model_id"
+]
  2. Addedv0.68.2

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavior burden and delivers two non-obvious facts: the operation is mutating but non-destructive, and the frameworks propagated to the model remain selected. It still omits auth/permission needs and reversibility.

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?

Two short sentences, front-loaded with the action and its key side effect; nothing is wasted.

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?

An output schema exists, so return values need no explanation, and the description covers the main mutation semantics. Given no annotations, it could add permission or reversibility details, but what is present is largely sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description usefully equates 'tag' with the group id and confirms model_id is the item removed, adding vocabulary meaning beyond the schema's terse descriptions. server_version remains undocumented in both.

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?

States a specific verb and resource (remove a model from a tag) and clarifies the mutation scope. It implicitly differentiates from add_model_to_group by naming the inverse operation, but never names a sibling explicitly.

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?

Usage is implied by the name and the 'Remove a model from a tag' phrasing; the description gives no explicit when/when-not guidance or routing to alternatives like add_model_to_group or delete_group.

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