Skip to main content
Glama

delete_profile

Deletes a database-saved MCP profile and reactivates any matching built-in or startup-file profile; watch history stays keyed by the profile name.

Instructions

Delete a database-saved MCP profile.

If a built-in or startup-file profile has the same name, it becomes active again. Watch history remains keyed by profile name.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description still discloses two non-obvious consequences of the mutation: a shadowed built-in/startup-file profile becomes active again, and watch history keyed by profile name survives the deletion. It stops short of saying whether deletion is permanent or what happens if the named profile doesn't exist.

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?

Three short statements, front-loaded with the action and followed by the two side effects; nothing is redundant. Minor wasted whitespace and an unstated connection between the two trailing sentences keep it below top marks.

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 single-parameter mutation with an output schema to carry return details, the description covers the essential post-deletion state. What's missing is failure behavior for unknown names and confirmation that deletion is irreversible.

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 0% and the only parameter is a bare 'Name' string, but the description's mention of profile names and built-in profiles with 'the same name' makes clear the parameter is the profile name to delete. It adds modest meaning without resolving case-sensitivity or name-format questions.

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 and resource ('Delete a database-saved MCP profile') and the qualifier 'database-saved' scopes it against the built-in/startup-file profiles mentioned next, so the agent can tell it apart from save_profile without another schema. The object of the operation is unambiguous.

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

Usage Guidelines3/5

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

The scope constraint ('database-saved') implies this only applies to saved profiles, and the fallback sentence hints at what happens when a same-named built-in exists. However, it never states when to choose this over save_profile or what to do with built-in profiles, leaving prerequisites to inference.

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