Skip to main content
Glama

HeyIdentity

add_user

Adds a fictional test user. user: { key, display_name?, sub?, icon?, access_token_sub?, claims?: { name: string|number|boolean|string[] }, claim_targets?: { name: both|id_token|access_token }, sign_in_outcome?: normal|access_denied|temporarily_unavailable|interaction_required|refresh_revoked (Pro) }.

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": {
      "configuration_id": "<configuration_id>",
      "user": "<user>"
    },
    "name": "add_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesThe user, as in the Agent API. A fictional test user. On edit, fields left out keep their value; claims, when given, replaces the user's claims.
configuration_idYesThe configuration id (from create_tenant or get_tenant).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 add two useful behavioral facts: the user is fictional test data and non-normal sign_in_outcome values are gated behind a Pro plan; but it says nothing about duplicate-key behavior, permissions needed, or what the call returns.

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-loads the one-line purpose, then the parameter map. Dense but efficient; the field enumeration largely mirrors the schema, which is mild redundancy rather than bloat.

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 2-parameter creation tool with full schema coverage this is close to sufficient, but with no annotations and no output schema an agent still lacks confirmation of what a successful add returns or how conflicts are handled.

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%, so every field is already documented in the input schema. The description restates the field list with optionality markers and enum values but adds no new meaning beyond that baseline.

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: 'Adds a fictional test user.' That separates it from edit_user and remove_user by verb alone, though it never names those siblings explicitly.

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 by the verb 'Adds' – there is no statement of when to choose this over add_client or edit_user, and no note that the configuration_id must come from create_tenant or get_tenant (that only appears in the schema).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources