Skip to main content
Glama
Sign In
COR MCP Server

COR MCP Server

by fxckcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

cor_delete_allocation

Delete a resource allocation by providing its allocation ID.

Instructions

Delete a resource allocation.

Args: allocation_id: The allocation ID

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": {
      "allocation_id": "<allocation_id>"
    },
    "name": "cor_delete_allocation"
  }
}

Input Schema

NameRequiredDescriptionDefault
allocation_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

The description only says 'Delete a resource allocation' without disclosing any side effects, such as cascading deletes, reversibility, or error handling. With no annotations, the description should cover these behavioral aspects.

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?

The description is efficient, using two sentences to convey purpose and argument. It is front-loaded and contains no fluff, though it could be more informative without being verbose.

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 simple delete operation with one parameter and an output schema, the description is adequate but missing key context like what the output represents or confirmation of deletion. It is minimally complete.

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 parameter description 'The allocation ID' merely restates the parameter name and schema type (integer or string). With 0% schema description coverage, the description adds no meaningful guidance on format, constraints, or source of the ID.

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 clearly states 'Delete a resource allocation,' which is a specific verb and resource. This distinguishes it from sibling tools like cor_save_allocation.

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?

No guidance is provided on when to use this tool versus alternatives, or any prerequisites for deletion. The description lacks context for appropriate use.

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