Skip to main content
Glama

dropbox_get_account

Read-onlyIdempotent

Retrieve the current Dropbox account profile using an access token to confirm identity and view account details.

Instructions

Get the current Dropbox account profile.

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

Input Schema

NameRequiredDescriptionDefault
access_tokenNoDropbox access token

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds only the notion of 'current' account (i.e., resolved from the credential), and says nothing about what the profile contains or whether fields vary by account type.

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?

A single short sentence with the resource front-loaded and no filler. It is appropriately sized, though so terse that it borders on under-specification rather than crisp completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a trivial read-only getter with full annotation coverage and a documented single param, the description is barely adequate. With no output schema, an agent gets no hint of the returned profile fields (email, name, account id, etc.), which would have been the one valuable addition here.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

One parameter at 100% schema description coverage ('Dropbox access token'), so the schema already explains it. The description adds no meaning about token source, scopes required, or per-token identity — baseline 3 applies when the schema does the work.

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 specific verb and resource ('Get', 'the current Dropbox account profile') and implicitly scopes to the authenticated account. It is distinguishable from the Dropbox siblings (list_folder, search, read_file) by resource, though it never explicitly contrasts with them.

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

Usage Guidelines2/5

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

No indication of when to call this versus other Dropbox tools, nor any prerequisite such as needing a valid access token or that the token determines whose profile is returned. The agent must infer all usage context from the name.

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