Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

projects_use

Set a project as the active profile so cli commands target its data, entities, and users. Resolves the project and saves credentials, requiring an active billing account.

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

TableJSON 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.2/5.0
Behavior4/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 well: it discloses the resolution-then-store flow, the apiKey vs automatic transfer-token exchange behavior, and the persistent side effect of saving active-profile credentials. It omits what happens to a previously active profile on overwrite and error modes, keeping it shy of a 5.

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?

Four tight sentences, front-loaded with purpose and effect, followed by mechanism, prerequisites, and return values. Every sentence carries distinct information with no redundancy.

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?

There is no output schema, and the description compensates by naming the returned fields (profile name, org id, API URL, auth method). Combined with the stated prerequisites and credential flow, an agent has enough to invoke it correctly, though overwrite/error behavior is unaddressed.

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%, so the schema already documents id (name/org id/UUID prefix), the optional ak_... apiKey, and the accountId default. The description restates the apiKey exchange semantics without adding new syntax or format detail, 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+resource ('Connect to a project and save it as the active profile') and clarifies downstream effect on the 'cli' tool's data, entities, and users commands. This clearly separates it from sibling tools like projects_list, projects_create, and accounts_use.

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 explicit prerequisites — an active billing account (pointing to accounts_use) and an Active project (pointing to projects_list) — which routes the agent to the right siblings for setup. It doesn't state an explicit 'when not to use this' condition, but the context is clear.

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