Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

config_remove

Deletes a saved project profile and its local credentials and settings from the CLI configuration. It does not delete the project or revoke server-side tokens; use projects_delete instead.

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

TableJSON 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?

No annotations are provided, so the description carries the full burden, and it does so well: it discloses the exact scope of destruction (local credentials and settings only), clarifies what is NOT affected (server-side project, tokens), and specifies the return behavior ('confirmation, or a not-found message'). This is materially more than the schema conveys.

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 tightly packed sentences, front-loaded with the action and scope, then the boundary condition, then the discovery hint and return behavior. No filler; every clause earns its place.

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?

For a single-parameter local mutation with no annotations and no output schema, the description covers everything an agent needs: scope of deletion, exclusion of server-side effects, the sibling alternative, the prerequisite for valid names, and the return outcome. Nothing 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 coverage is 100%, so the single 'profile' parameter is already fully documented, including the config_show pointer. The description adds no syntax or format detail beyond the schema, so the 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 and resource ('Delete a saved project profile from the local CLI configuration') with the scoping qualifier 'local' front-loaded. The agent can immediately distinguish this from server-side siblings like projects_delete. No ambiguity about what is being removed.

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?

Explicitly delineates when-not-to-use ('does not delete the project or revoke tokens server-side') and names the alternative tool ('to remove the project itself, use projects_delete'). It also provides the prerequisite discovery step ('Run config_show to see profile names'). Fully self-routing.

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