Skip to main content
Glama
Sign In
Anythink-MCP

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Remove a saved project profile

config_remove
Destructive

Remove a saved project profile from local CLI configuration, deleting only locally stored credentials and settings. Does not delete the project or revoke server-side tokens.

Instructions

Delete a saved project profile from the local CLI configuration. Removes only the locally stored credentials and settings — it does not delete the project or revoke tokens server-side (to remove the project itself, use 'projects_delete'). Run 'config_show' to see profile names. Returns confirmation, or a not-found message.

Input Schema

NameRequiredDescriptionDefault
profileYesName of the profile to remove from local config. See 'config_show' for valid names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.27
    • removedInput schema / description
      Removed value: -"Delete a saved project profile from the local CLI configuration. Removes only the locally stored credentials and settings — it does not delete the project or revoke tokens server-side (to remove the project itself, use 'projects_delete'). Run 'config_show' to see profile names. Returns confirmation, or a not-found message."
    • removedInput schema / title
      Removed value: -"config_remove"
  2. Changed2 schema fields changedv0.2.21
    • changedInput schema / description
      Previous value: -"Remove a project profile from the CLI configuration"New value: +"Delete a saved project profile from the local CLI configuration. Removes only the locally stored credentials and settings — it does not delete the project or revoke tokens server-side (to remove the project itself, use 'projects_delete'). Run 'config_show' to see profile names. Returns confirmation, or a not-found message."
    • changedInput schema / properties / profile / description
      Previous value: -"Profile name to remove"New value: +"Name of the profile to remove from local config. See 'config_show' for valid names."
  3. First observedv0.2.6

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only supply destructiveHint=true, but the description adds the crucial semantic that destruction is scoped to local credentials/settings and that no server-side revocation occurs — a distinction an agent could easily get wrong. It also discloses the outcome shape ('confirmation, or a not-found message').

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?

Three sentences, each doing distinct work: scope of deletion, boundary/exclusion with alternative, and return behavior plus name discovery. The core action is front-loaded with no filler.

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?

No output schema exists, yet the description covers the return contract ('confirmation, or a not-found message'), the local-vs-server scope, and how to find valid inputs. Nothing an agent needs to invoke this safely is missing.

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 100% for the single 'profile' parameter, so the schema already documents name and source of valid values. The description's 'Run config_show to see profile names' reinforces this but adds nothing the schema doesn't already state; baseline 3 applies.

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+resource+scope: 'Delete a saved project profile from the local CLI configuration.' The qualifier 'from the local CLI configuration' immediately distinguishes it from the similarly named sibling 'projects_delete', which the description also explicitly names.

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?

Gives an explicit when-not clause ('it does not delete the project or revoke tokens server-side') with the correct alternative named ('to remove the project itself, use projects_delete'). It also routes the agent to 'config_show' to discover valid profile names, covering the pre-call lookup step.

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