Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Unlink your CommunityCAD account

unlink_account
Destructive

Sign out by revoking this computer's CommunityCAD sign-in and deleting the local credentials, so the device is no longer linked to your account.

Instructions

Sign out: revoke this computer's CommunityCAD sign-in and delete it locally.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "unlink_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, but they do not say WHAT is destroyed. The description adds that key detail: the sign-in is revoked (server-side) and the credential is removed from this computer specifically, local rather than account-wide. It stops short of saying whether the action is reversible or requires re-authentication afterwards.

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?

A single sentence, front-loaded with the user-facing framing 'Sign out:', followed by the precise technical effect. No redundant restatement of the name or title.

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-parameter, no-output-schema tool, the description covers the essentials: what is revoked and what is deleted locally. The only meaningful gap is post-condition behavior — whether other devices, tokens, or cached data are affected and whether re-linking is needed.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the empty schema is self-explanatory. Baseline 4 applies for a no-parameter tool.

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 concrete action pair — revoke the sign-in for this machine and delete the local credential — which is more specific than the name 'unlink_account' alone. It does not explicitly distinguish itself from the sibling 'link_account', so an agent must infer the inverse relationship.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Sign out' implies the situation in which to call it, but there is no explicit when-not guidance, no mention of prerequisites (e.g. must currently be signed in), and no pointer to 'link_account' for the reverse operation. Usage is implied rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.