Skip to main content
Glama
Sign In
ACC MCP

ACC MCP

by nhantruong96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

acc_logout

Log out by discarding the stored session token before switching Autodesk accounts; sign in again to start a new session.

Instructions

Discard the stored 3-legged session (refresh token). Use before switching Autodesk accounts; sign in again with acc_login.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The description adds context beyond the minimal annotations (readOnlyHint: false) by specifying exactly what is discarded (refresh token) and the 3-legged session. This is consistent with the non-read-only annotation, and no contradictions exist.

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?

The description is two sentences, front-loaded with the action, and every word earns its place. It is succinct and well-structured.

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?

For a simple zero-parameter tool with an output schema, the description fully covers purpose, usage context, and behavioral effect. It is complete for the tool's complexity.

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 has zero parameters, so the description needs no param details. Per the rubric, 0 parameters defaults to a baseline score of 4, and the description adds no unnecessary parameter context.

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?

The description clearly states the tool discards the stored 3-legged session (refresh token), using a specific verb and resource. It distinguishes from siblings like acc_login (which creates a session) and acc_auth_status (which checks status).

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?

Explicit guidance is given: 'Use before switching Autodesk accounts' and 'sign in again with acc_login'. This provides a clear when-to-use and names an alternative tool, satisfying the top criterion.

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