Skip to main content
Glama
Sign In
SmartBear MCP server

SmartBear MCP server

Official
by SmartBear
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Contract Testing: Admin Get User

contract-testing_admin_get_user
Read-onlyIdempotent

Retrieve details for a specific user by UUID to support administrative account lookup and review.

Instructions

Retrieve details for a specific user by UUID (admin).

Toolset: Admin

Parameters:

  • userId (string) required: UUID of the user

Input Schema

NameRequiredDescriptionDefault
userIdYesUUID of the user

Output Schema

NameRequiredDescriptionDefault
nameNo
typeNo
uuidNo
emailNo
_linksNo
activeNo
lastNameNo
seatTypeNo
_embeddedNo
createdAtNo
firstNameNo
lastLoginNo
updatedAtNo
externalIdNo
externalIdpIdNo
typeDescriptionNo
identityProviderIdNo
externalIdpUsernameNo
authenticationSourceNo
lastTimeTokenAccessedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.43.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "EmbeddedLink": {
+      "additionalProperties": {},
+      "properties": {
+        "href": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "templated": {
+          "type": "boolean"
+        },
+        "title": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "Permission": {
+      "additionalProperties": {},
+      "properties": {
+        "description": {
+          "type": "string"
+        },
+        "group": {
+          "type": "string"
+        },
+        "label": {
+          "type": "string"
+        },
+        "scope": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "UserRole": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        },
+        "permissions": {
+          "items": {
+            "$ref": "#/$defs/Permission"
+          },
+          "type": "array"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "UserTeam": {
+      "additionalProperties": {},
+      "properties": {
+        "_links": {
+          "additionalProperties": {},
+          "properties": {
+            "pf:integrations": {
+              "$ref": "#/$defs/EmbeddedLink"
+            },
+            "pf:membership": {
+              "$ref": "#/$defs/EmbeddedLink"
+            },
+            "self": {
+              "$ref": "#/$defs/EmbeddedLink"
+            }
+          },
+          "type": "object"
+        },
+        "name": {
+          "type": "string"
+        },
+        "uuid": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "_embedded": {
+      "additionalProperties": {},
+      "properties": {
+        "roles": {
+          "items": {
+            "$ref": "#/$defs/UserRole"
+          },
+          "type": "array"
+        },
+        "teams": {
+          "items": {
+            "$ref": "#/$defs/UserTeam"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "_links": {
+      "additionalProperties": {},
+      "properties": {
+        "pf:tokens": {
+          "$ref": "#/$defs/EmbeddedLink"
+        },
+        "self": {
+          "$ref": "#/$defs/EmbeddedLink"
+        }
+      },
+      "type": "object"
+    },
+    "active": {
+      "type": "boolean"
+    },
+    "authenticationSource": {
+      "type": "string"
+    },
+    "createdAt": {
+      "type": "string"
+    },
+    "email": {
+      "type": "string"
+    },
+    "externalId": {
+      "type": "string"
+    },
+    "externalIdpId": {
+      "type": "string"
+    },
+    "externalIdpUsername": {
+      "type": "string"
+    },
+    "firstName": {
+      "type": "string"
+    },
+    "identityProviderId": {
+      "type": "string"
+    },
+    "lastLogin": {
+      "type": "string"
+    },
+    "lastName": {
+      "type": "string"
+    },
+    "lastTimeTokenAccessed": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    },
+    "seatType": {
+      "type": "string"
+    },
+    "type": {
+      "anyOf": [
+        {
+          "const": 0,
+          "type": "number"
+        },
+        {
+          "const": 1,
+          "type": "number"
+        }
+      ]
+    },
+    "typeDescription": {
+      "type": "string"
+    },
+    "updatedAt": {
+      "type": "string"
+    },
+    "uuid": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Addedv0.40.0
  3. Removedv0.34.0
  4. First observedv0.27.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only the admin-permission qualifier, which is genuinely useful context, but says nothing about failure behavior for unknown UUIDs or scoping across teams.

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?

Front-loaded with the action and resource in one sentence, then a compact toolset label and parameter note. The parameter block largely restates the input schema, which is mild redundancy, but nothing is bloated.

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 required string parameter and an output schema present, the description covers what is needed to invoke the tool. It is thin on the admin-permission context and on what the returned user object contains, but the output schema relieves the latter burden.

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 userId parameter is documented identically in both schema and description, so the description adds no meaning beyond the schema. Baseline 3 applies for a one-parameter tool whose 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+resource ("Retrieve details for a specific user") with the identifier type (UUID) and an admin scope qualifier, which distinguishes it from list-style siblings such as contract-testing_admin_list_users. It never names a sibling explicitly, so differentiation is only implied by the singular "specific user" phrasing.

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 when-to-use or when-not-to-use guidance is given, and no alternatives are named. An agent is left to infer that this is the lookup-by-known-UUID path versus listing users to discover UUIDs, and the "(admin)" tag is the only hint that elevated permissions apply.

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