Skip to main content
Glama

Get my TMDB account

get_account
Read-only

Retrieve details of the configured TMDB account, including ID, username, name, language, and country.

Instructions

Details of the configured TMDB account: ID, username, name, language and country.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/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 adds that the account is the pre-configured one (no account parameter needed) and enumerates the returned fields, but says nothing about authentication requirements, failure modes when no session exists, or response shape beyond the field list.

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 that front-loads the resource and then lists outputs; nothing redundant. It is slightly clipped (a fragment rather than a full sentence) but that costs no comprehension.

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?

For a zero-parameter read with no output schema, the description carries the return-value burden well by listing the fields. It omits any note on auth/session failure behavior, which is the only meaningful remaining gap.

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 takes zero parameters, so the baseline is 4. The description usefully clarifies that the account is implicitly the configured one, explaining why no identifier is required.

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+resource ('Details of the configured TMDB account') and enumerates the returned fields (ID, username, name, language, country), so an agent knows exactly what this read returns. It does not explicitly distinguish itself from account-scoped siblings like get_account_lists or get_account_items, so it stays short of 5.

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?

There is no explicit when-to-use guidance, no prerequisite notes (e.g. that it reveals the account ID needed by the account_items/lists/states tools), and no mention of alternatives. Usage is only implied by the name and the word 'configured'.

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