Skip to main content
Glama

user_getProfile

Retrieve an Operaton user profile by ID to get first name, last name, and email for identifying or displaying user details.

Instructions

Retrieve the profile of a specific Operaton user by ID. Returns firstName, lastName, and email.

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": {
      "id": "<id>"
    },
    "name": "user_getProfile"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.3.0
    • addedInput schema / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "id"
      +]
  2. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does convey the read-only nature via "Retrieve" and discloses the returned fields (firstName, lastName, email), which substitutes for the missing output schema. It omits notable behavior: what happens when the ID does not exist, whether the response includes other fields, and any authentication requirements.

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?

Two short sentences with the purpose front-loaded and the return values immediately after; nothing is padding or repeated from the name.

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 one-parameter read tool with no annotations and no output schema, the description supplies the operation, the identifier, and the return fields, which is close to sufficient. The remaining gaps, error behavior and ID format, are minor for a lookup this simple.

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 0% for the single `id` parameter, and the description only adds that it identifies a "specific Operaton user". That confirms intent but provides no format, sourcing, or validity constraints for the identifier.

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?

The description opens with a specific verb and resource ("Retrieve the profile of a specific Operaton user by ID") and names the fields returned, so the operation is unambiguous. It does not explicitly contrast itself with sibling tools such as user_list or user_updateProfile, which keeps it from a 5.

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?

"by ID" implies this is a point lookup that requires a known user identifier, which is a usable hint for selecting it over user_list. However, there is no explicit statement of when to use this versus the list or update siblings, and no prerequisites such as permissions or ID format are given.

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