Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Link your CommunityCAD account

link_account

Signs in to CommunityCAD by generating a clickable approval link, then saves the account link on this computer; optionally requests upload permission for the linked account.

Instructions

Sign in to CommunityCAD: the user approves a link on the website.

Returns at once with the approval link (show it to the user as a clickable link) and opens it in their browser when possible. Approval is picked up in the background and saved, so the next tool call is signed in; the user doesn't need to say "done". Calling again while it waits returns the same link. status "pending" means it is still waiting for the user's approval; that is normal, not a connection problem. The sign-in is saved on this computer only and shows in the account as " on ". allow_uploads=true asks the user to also allow uploads; when already linked, it asks them to approve just that permission (call again to finish, like the first link).

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": "link_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoKeep checking (up to ~50 seconds) before answering. Not needed: approval is picked up in the background.
allow_uploadsNoAlso ask for permission to upload (only after the user said they want to upload). Works when already linked too.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.6/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: the call returns immediately with an approval link that should be shown as clickable, the browser may be opened, approval is picked up in the background so the next call is signed in, repeated calls while waiting return the same link, and status 'pending' is normal rather than an error. It also discloses persistence scope ('saved on this computer only') and how the link appears in the account, none of which the annotations convey.

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?

Front-loads the core action in the first sentence and then layers the behavioral caveats in a logical order. It runs a little long in places ('the user doesn't need to say "done"'), but each sentence carries operational information rather than filler.

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?

With no output schema, the description carries the burden of describing return values and does so — approval link, clickable presentation, pending status meaning. For a two-parameter, zero-required, open-world auth tool, nothing an agent needs in order to call and interpret it 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 schema already documents both booleans; the description nonetheless adds useful meaning by saying wait is unnecessary because approval is picked up in the background, and that allow_uploads is conditional on the user having expressed intent to upload, including the already-linked re-approval flow.

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 — 'Sign in to CommunityCAD' via a website approval link — which is instantly distinguishable from siblings like account_status and unlink_account. An agent knows exactly what capability this tool provides without reading 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 Guidelines4/5

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

Gives clear usage context: call when the user needs to sign in, and call with allow_uploads=true only after the user has said they want to upload, including a note on repeating the call to finish an already-linked permission grant. It does not explicitly route the agent to account_status to check existing link state first, so it stops short of full when/when-not guidance.

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