Skip to main content
Glama

get_user

Retrieves detailed information for a specified username, enabling administrators to inspect user account details and verify configuration in Ambari-managed Hadoop clusters.

Instructions

Get detailed information about a specific user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_name": "<user_name>"
    },
    "name": "get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
user_nameYesThe username to retrieve details for

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.8.2
    • addedInput schema / properties / user_name / description
      Added value: +"The username to retrieve details for"
  2. Changed4 schema fields changedv3.7.5
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / user_name / title
      Removed value: -"User Name"
    • removedOutput schema / properties / result / title
      Removed value: -"Result"
    • removedOutput schema / title
      Removed value: -"_WrappedResult"
  3. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it says nothing about behavior for unknown usernames, required permissions, or rate limits. 'Detailed information' hints at depth of return, but that is also covered by the output schema, so it adds little.

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 front-loaded sentence with no filler. It is efficient, though its brevity is closer to under-specification than to economical 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?

With one fully documented parameter, an output schema, and a simple read operation, the definition is minimally sufficient. It leaves open the error/empty case and any permission requirements, which matter for a lookup by username.

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?

Schema description coverage is 100% and the single parameter is documented as 'The username to retrieve details for', so the schema does the work. The description only echoes that a user identifier is required, adding no format or resolution rules.

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 ('Get') and resource ('detailed information about a specific user'), which is clear enough to separate it from the sibling list_users by singular-vs-listing semantics. It stops short of explicitly naming that sibling as the alternative for enumeration.

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: 'a specific user' suggests it is for a single known username rather than browsing, but there is no explicit when-to-use, when-not, or pointer to list_users for enumeration. An agent must infer the routing.

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