Skip to main content
Glama
trafficmorph-gif

tm-mcp

by trafficmorph-gif
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

tm_delete_variables_set

Destructive

Delete a variables set; fails immediately if attached to profiles, listing them for detaching before retry.

Instructions

Delete a variables set. Fails fast (HTTP 400) if the set is still attached to any profile — the server does NOT auto-detach.

The server-side error message names the referencing profile(s) so the caller can detach them first. The MCP layer preserves that message verbatim in the typed ToolError so the AI host can read it back to the user. Example error text::

Can't delete 'users-fixture' — still attached to profiles:
loadtest-api.example.com, smoke-test. Detach it from those
profiles first.

To delete an attached set, the typical recovery is to call :func:tm_update_profile on each referencing profile with an updated variables-set attachment list that omits this set's id, then retry the delete. (The variables-set attachment is a property of the profile, not of the set — managed via the profile's update path, not via a separate endpoint here.)

Returns {"variables_set_id": <id>, "deleted": True} on success. A 400 / "Variables set not found" or "still attached" surfaces as a typed :class:ToolError — caller can react without parsing message text beyond the error string itself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
variables_set_idYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

The description adds value beyond the `destructiveHint` annotation by explaining that it does not auto-detach, including the error message format, and the success response. No contradiction with annotations.

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 well-structured with the main action and crucial constraint first, followed by error details, recovery, and response. Every sentence is informative and necessary.

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?

Given a single required parameter and no output schema, the description is thorough: it covers the constraint, error behavior, recovery path, and success output, making the tool fully understandable.

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?

With 0% schema description coverage, the description carries full burden. It implies the parameter is the ID of the set to delete, but does not explicitly state it. However, for a single required integer parameter, the meaning is clear from context.

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 it deletes a variables set and distinguishes from siblings by detailing a specific constraint (fails if attached to a profile). The verb 'Delete' and resource 'variables set' are explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-not to use (if set is attached to a profile) and gives recovery steps: call tm_update_profile to detach first. Also notes error handling and alternative action via `tm_update_profile`.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/trafficmorph-gif/tm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server