Skip to main content
Glama
Sign In
Anythink-MCP

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Sign out

logout

Remove saved credentials for a project profile from local CLI config to disconnect or clear a stale token. Deletes only the stored profile locally; omit profile to remove the active one.

Instructions

Remove the saved credentials for a project profile from local CLI config. Use this to disconnect from a project or clear a stale token; it deletes only the stored profile locally and does not revoke the token server-side or affect the project. Omit the profile to remove the currently active one. Run 'config_show' to see profile names.

Input Schema

NameRequiredDescriptionDefault
profileNoName of the profile to remove. Defaults to the active profile. See 'config_show' for names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.27
    • removedInput schema / description
      Removed value: -"Remove the saved credentials for a project profile from local CLI config. Use this to disconnect from a project or clear a stale token; it deletes only the stored profile locally and does not revoke the token server-side or affect the project. Omit the profile to remove the currently active one. Run 'config_show' to see profile names."
    • changedInput schema / properties / profile / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"logout"
  2. Changed2 schema fields changedv0.2.21
    • changedInput schema / description
      Previous value: -"Remove saved credentials for a project profile"New value: +"Remove the saved credentials for a project profile from local CLI config. Use this to disconnect from a project or clear a stale token; it deletes only the stored profile locally and does not revoke the token server-side or affect the project. Omit the profile to remove the currently active one. Run 'config_show' to see profile names."
    • changedInput schema / properties / profile / description
      Previous value: -"Profile name to remove (uses active profile if omitted)"New value: +"Name of the profile to remove. Defaults to the active profile. See 'config_show' for names."
  3. First observedv0.2.6

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare destructiveHint=false; the description earns credit by explaining why — deletion is confined to local stored credentials, the server-side token is untouched, and the project is unaffected. It also discloses the default behavior when the profile is omitted.

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 tight sentences; the destructive scope ('local only') is front-loaded ahead of the usage conditions and the sibling pointer. Zero filler.

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 zero-required-param, no-output-schema tool, this covers purpose, scope, default behavior, and where to find profile names. It does not mention success/failure feedback or what happens for a nonexistent profile, a minor gap.

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% and the single parameter is fully documented, including its default and the 'config_show' lookup hint, which the description merely echoes. Baseline 3 applies because the description adds no syntax or format detail beyond the schema.

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 ('remove the saved credentials for a project profile from local CLI config') with an explicit scope limiter ('locally'). An agent can distinguish this from config_show, config_remove, login, and projects_use without opening any schema.

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?

Gives clear when-to-use conditions ('disconnect from a project or clear a stale token') and an explicit boundary ('does not revoke the token server-side or affect the project'), plus a pointer to 'config_show' for profile names. It stops short of naming a specific sibling as the alternative for related jobs (e.g. config_remove), so it is strong but not fully 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