Skip to main content
Glama
Sign In
Anythink-MCP

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Switch the active project

projects_use

Connect to a project and save it as the active profile so CLI commands target its data, entities, and users; stores your API key or exchanges a transfer token for project-scoped credentials.

Instructions

Connect to a project and save it as the active profile so the 'cli' tool's data, entities, users, and other commands target it. Resolves the project, then either stores the API key you pass or exchanges a transfer token for project-scoped credentials automatically. Requires an active billing account (set one with 'accounts_use'); the project must be Active (see 'projects_list'). Returns the saved profile name, org id, API URL, and auth method.

Input Schema

NameRequiredDescriptionDefault
idYesProject to connect to — its name, org id, or UUID (a unique prefix is accepted). Find these via 'projects_list'.
apiKeyNoOptional project API key (ak_...). If omitted, a project-scoped token is generated automatically via transfer-token exchange.
accountIdNoBilling account id the project belongs to. Defaults to the active account set via 'accounts_use'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.27
    • removedInput schema / description
      Removed value: -"Connect to a project and save it as the active profile so the 'cli' tool's data, entities, users, and other commands target it. Resolves the project, then either stores the API key you pass or exchanges a transfer token for project-scoped credentials automatically. Requires an active billing account (set one with 'accounts_use'); the project must be Active (see 'projects_list'). Returns the saved profile name, org id, API URL, and auth method."
    • changedInput schema / properties / accountId / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • changedInput schema / properties / apiKey / type
      Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
    • removedInput schema / title
      Removed value: -"projects_use"
  2. Changed4 schema fields changedv0.2.21
    • changedInput schema / description
      Previous value: -"Connect to a project and save it as the active profile. Exchanges a transfer token for project-scoped credentials."New value: +"Connect to a project and save it as the active profile so the 'cli' tool's data, entities, users, and other commands target it. Resolves the project, then either stores the API key you pass or exchanges a transfer token for project-scoped credentials automatically. Requires an active billing account (set one with 'accounts_use'); the project must be Active (see 'projects_list'). Returns the saved profile name, org id, API URL, and auth method."
    • changedInput schema / properties / accountId / description
      Previous value: -"Billing account ID (uses active account if omitted)"New value: +"Billing account id the project belongs to. Defaults to the active account set via 'accounts_use'."
    • changedInput schema / properties / apiKey / description
      Previous value: -"API key for the project (generates token if omitted)"New value: +"Optional project API key (ak_...). If omitted, a project-scoped token is generated automatically via transfer-token exchange."
    • changedInput schema / properties / id / description
      Previous value: -"Project name, org ID, or UUID (or prefix)"New value: +"Project to connect to — its name, org id, or UUID (a unique prefix is accepted). Find these via 'projects_list'."
  3. First observedv0.2.6

TDQS

A4.8/5.0
Behavior5/5

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

Annotations provide only destructiveHint=false, so the description carries the full behavioral burden and does so: it discloses the state mutation (persisting an active profile that redirects later commands), the credential flow (stores passed API key vs. auto-exchanges a transfer token), auth prerequisites, and the return payload. This goes well beyond the structured fields.

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?

Four tight sentences, front-loaded with the primary effect before prerequisites and return values. Dense but every sentence conveys distinct, non-redundant information; only marginal trimming is possible.

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 enumerates the returned values (profile name, org id, API URL, auth method) and covers prerequisites, credential handling, and state impact. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning: it explains the interaction between params (if apiKey is omitted a project-scoped token is generated) and that accountId defaults to the active account. This clarifies the optional-parameter tradeoffs beyond the schema text.

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 ('Connect to a project and save it as the active profile') and ties the effect to the 'cli' tool's downstream behavior, clearly differentiating it from projects_list/projects_create/projects_delete. An agent knows exactly what this does without opening the schema.

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 names prerequisites (active billing account, set via 'accounts_use') and a precondition (project must be Active, see 'projects_list'), plus routes the agent to the sibling tools for both. When-to-use is fully inferable and alternatives are named.

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