Skip to main content
Glama
Mipiti

Mipiti MCP Server

by Mipiti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Group

get_group

Fetch a tag by ID and its member model IDs for read-only lookups. Use list_groups to discover available tag IDs.

Instructions

Get one tag by ID, with its member model ids. Read-only; no side effects.

Returns {id, workspace_id, name, description, created_at, model_ids}. Discover tag IDs with list_groups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesID of the tag.
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": "ID of the tag.",
+  "type": "string"
+}
    • removedInput schema / properties / system_id
      Removed value: -{
-  "description": "ID of the system to retrieve.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "server_version",
-  "system_id"
-]New value: +[
+  "server_version",
+  "group_id"
+]
  2. Addedv0.68.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does state the safety profile ('Read-only; no side effects'), which is exactly the behavioral fact an agent needs before calling. It stops short of permissions or error behavior (e.g., what happens for an unknown ID), so it is solid but not exhaustive.

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?

Three short sentences, each earning its place: purpose, safety profile, return shape, and ID discovery. The scoping verb phrase is front-loaded.

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 restating the return fields is redundant but harmless, and the description adds the safety profile and the ID-discovery path an agent needs. The main remaining gap is that server_version is unexplained and the group/tag naming is never reconciled.

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 coverage is 50%: group_id is already documented in the schema, and server_version has no description anywhere. The description's 'by ID' adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 ('Get one tag by ID, with its member model ids'), and the phrase 'one ... by ID' distinguishes it from the sibling list_groups, which it names. The only wrinkle is the group/tag terminology mismatch between the tool name (get_group) and the description ('tag'), which adds minor ambiguity about whether these are the same entity.

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?

Explicitly tells the agent how to obtain a valid ID ('Discover tag IDs with list_groups'), which routes it to the right sibling for the prerequisite step. There is no explicit when-not guidance, but for a simple fetch-by-ID tool the context is clear.

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