Skip to main content
Glama
Sign In
SuperDev

SuperDev

by Xsxdot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Release test database

release_test_database

Release an isolated real test environment before its lease expires by providing the lease ID, freeing resources and preventing unintended retention.

Instructions

Release an isolated real test environment before its lease expires.

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": {
      "lease_id": "<lease_id>"
    },
    "name": "release_test_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
lease_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.2/5.0
Behavior3/5

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

Without annotations, the description must convey side effects. It says 'Release' and mentions lease expiration, but it does not state whether the action is destructive (e.g., deletes data) or simply marks the resource as available. The impact of releasing is not fully transparent.

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 a single, concise sentence with no unnecessary words, clearly stating the action and the condition related to lease expiry.

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?

Given the simplicity of the operation and the absence of an output schema, the description covers the essential context. It does not mention prerequisites (e.g., must have an active lease) or return behavior, but for a release operation this is likely 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?

The single parameter lease_id is self-explanatory from its name, but the description provides no additional context. Since the schema has no description, the parameter semantics are adequate but not enriched.

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 the tool releases an isolated real test environment, using the verb 'Release' and specifying the object. It distinguishes from sibling tools like renew_test_database and acquire_test_database by implying the process of giving up a lease.

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 phrase 'before its lease expires' suggests this is for early release, but it does not explicitly contrast with alternatives like renew or list. However, in the context of siblings, the intended usage is fairly clear: when a test database is no longer needed.

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