Skip to main content
Glama
Sign In
ACC MCP

ACC MCP

by nhantruong96
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

acc_whoami

Read-only

Verify your Autodesk sign-in and list accessible ACC hubs to fetch account IDs for admin tasks.

Instructions

Show the signed-in Autodesk user (3-legged) and the ACC hubs the current credentials can see. Useful to verify access after login and to fetch hub (account) ids for the admin tools.

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_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description discloses that the tool requires 3-legged credentials and shows what the current credentials can see. This adds useful behavioral context about authentication and scoping, which the annotation alone does not provide.

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 concise and well-structured: two sentences, with the first stating the function and the second providing the use case. No unnecessary words or repetition.

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 and read-only annotation, the description fully covers what the tool does, why it is useful, and when to use it. No gaps in context.

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?

With zero parameters, the schema fully covers parameter semantics. The description adds no parameter details, but none are needed. The baseline of 4 for zero-parameter tools is appropriate.

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's function with a specific verb ('Show') and resource ('signed-in Autodesk user and ACC hubs'), and distinguishes it from sibling tools like acc_list_hubs by emphasizing the credential-scoped view. The mention of fetching hub ids for admin tools further clarifies its role.

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?

The description gives clear context for when to use it ('verify access after login' and 'fetch hub ids for admin tools'), but does not explicitly mention alternatives or when not to use it. This is clear usage context without exclusions, aligning with a score of 4.

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