Skip to main content
Glama
Sign In
errorbar

errorbar

by omnia-v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete dedicated endpoint

delete_dedicated_endpoint
DestructiveIdempotent

Permanently tear down a dedicated endpoint: runs a final meter to bill accrued GPU-hours, releases reserved GPUs, and marks it deleted so you stop paying for it.

Instructions

Tears down a dedicated endpoint: meters and bills the GPU-hours accrued since the last meter, frees the reserved GPUs, and marks it DELETED — the way to permanently stop paying for an endpoint. DELETE /v1/dedicated/{id} (API-key scope: platform:write). Returns: { ok: true } on success. Notes: Requires an OWNER/ADMIN minting user (403). 404 'Endpoint not found' (already-deleted endpoints also 404). MONEY: runs a final meter first (bills accrued GPU-hours), then releases the endpoint; soft-deleted (status DELETED, enabled=false) and excluded from later lists. Not reversible. Scope note: local dedicated apiKeyActor does not enforce key scopes.

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": "delete_dedicated_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesDedicated endpoint id (must belong to the key's workspace).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it destructive and non-readonly, but the description adds crucial behavioral context: a final meter/billing step, soft-delete semantics, exclusion from lists, non-reversibility, authorization scope, and the 404 behavior for already-deleted endpoints. This goes well beyond the annotations and fully discloses consequences.

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?

The description is dense but every sentence earns its place, covering action, billing effect, API details, permissions, error cases, and irreversibility. It is front-loaded with the core purpose and then layers supporting details efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, billing-affecting operation with no output schema, the description is complete: it states the response shape, required permissions, error behavior, side effects, and irreversibility. An agent has everything needed to invoke it correctly and understand consequences.

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?

The schema already provides 100% coverage for the single 'id' parameter, including a clear description. The tool description adds no additional parameter-level meaning beyond what the schema states, so the baseline of 3 is appropriate.

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 description states a specific verb ('Tears down') and resource ('dedicated endpoint'), and explains the result: billing accrued GPU-hours, freeing GPUs, marking DELETED, and stopping payments. It clearly distinguishes this from related endpoint operations like update or create.

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?

It explains exactly when to use this tool ('the way to permanently stop paying for an endpoint') and gives prerequisites (OWNER/ADMIN, workspace ownership). It doesn't explicitly name alternatives or say when not to use it, but the context is clear enough for an agent to select it appropriately.

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