Skip to main content
Glama
communitycad-mcp

communitycad-mcp

Official

Account and downloads left

account_status
Read-only

Check whether a CommunityCAD account is linked, view plan details and remaining daily/weekly downloads with reset times, or see signed-out download limits.

Instructions

Whether a CommunityCAD account is linked, the plan, downloads left today and this week, and when they reset. Signed out: the signed-out limit and what's left of it.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes one genuinely new behavioral fact: the tool works in a signed-out state and reports a separate signed-out limit. It says nothing about whether results are cached, whether it triggers network calls to the account service, or latency considerations.

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?

Two compact clauses, front-loaded with the primary result (link state and plan) before the quota details and the signed-out fallback. No filler, no repetition of the 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?

There is no output schema, so the description must carry the return shape, and it does by enumerating the fields an agent will receive in both linked and signed-out cases. It could go slightly further on how 'downloads left' reset windows are represented, but nothing essential for calling a zero-parameter read tool 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?

The input schema is empty (zero parameters) with 100% schema coverage, so the baseline is 4. There are no parameter semantics to explain and the description correctly does not invent any.

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?

The description names the resource (CommunityCAD account status) and enumerates the specific payload: link state, plan, downloads remaining today and this week, reset timing. That is far more specific than a name restatement. It stops short of explicitly distinguishing itself from siblings like check_download or link_account, so it lands at 4 rather than 5.

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?

Usage is only implied: read it when you need the account link state or remaining download quota. The clause 'Signed out: the signed-out limit and what's left of it' usefully signals the tool is callable while unauthenticated, but there is no explicit guidance on when to prefer this over the sibling check_download tool.

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