Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

logout

Remove saved project profile credentials from local CLI config to disconnect or clear a stale token. Omit profile to delete the active one; run config_show to view names.

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

TableJSON 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.1/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well, disclosing exactly what is destroyed (the locally stored profile) and explicitly what is NOT affected (server-side token not revoked, project unaffected). This is precisely the mutation context an agent needs before invoking.

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 sentences, front-loaded with purpose, then usage, then the practical note on finding profile names. Every sentence earns its place with no padding.

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 one-parameter tool with no annotations and no output schema, the description is complete: it covers purpose, effect, non-effects, and how to discover profile names. Nothing an agent needs to call it correctly 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% and the single parameter's description already documents the default-to-active behavior and the config_show reference. The description's 'omit the profile to remove the currently active one' essentially restates the schema default, adding no new syntax or meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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'), so the agent knows exactly what it does. It is distinguishable from login, but the sibling config_remove is never referenced, leaving potential overlap unexplained.

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 context ('disconnect from a project or clear a stale token') and a when-not caveat (does not revoke server-side). It also points to config_show for profile names, though it never contrasts with the closely related config_remove sibling.

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