Skip to main content
Glama
Sign In

Ankra

by ai.ankra
OverviewDiscussionsAdmin

Delete AI model

delete_ai_model
Destructive

Remove a model from the organisation's AI model catalog (the twin of ankra ai models delete); a lane that selected it falls back to its default. model is the catalog row id or key (list_ai_models). Needs ai.manage (organisation owners and admins).

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": {
      "model": "<model>"
    },
    "name": "delete_ai_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesThe model's catalog row id or its catalog key, as list_ai_models shows them.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the destructive/non-idempotent annotations, it discloses two things the annotations can't: the cascade effect that any lane selecting the model reverts to its default, and the required ai.manage permission (organisation owners and admins). It does not say whether the deletion is reversible or what happens if the model is still referenced elsewhere, which is the remaining gap for a destructive operation.

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 front-loaded sentence with the destructive consequence and permission requirement up front, no filler. The 'twin of `ankra ai models delete`' parenthetical is CLI trivia an agent cannot act on and is the one phrase not earning its place.

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?

For a one-parameter destructive tool with no output schema, the description covers what it deletes, the side effect on lanes, how to find the id, and the auth requirement. Missing only irreversibility/restore guidance, which matters for a non-idempotent destructive call.

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 100%, so the parameter is already documented, and the description's 'catalog row id or key' closely paraphrases it. Its only marginal addition is tying the value to list_ai_models, which is useful but not new semantics.

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?

States a specific verb (remove) and resource (model from the organisation's AI model catalog), and the catalog scope plus the lane-fallback consequence separates it cleanly from siblings like update_ai_model, create_ai_model and clear_ai_lane_model.

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 lane-fallback note implicitly frames this as the catalog-level delete rather than the lane-level unset, and it points to list_ai_models for obtaining the identifier. It never explicitly names a when-not-to-use case (e.g. use clear_ai_lane_model to detach a lane without deleting the model), so alternative routing is inferable but not stated.

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

All Ankra toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources