Skip to main content
Glama

HeyIdentity

create_tenant

Creates an unverified HeyIdentity test tenant with a working demo client and test user, accepting the current Terms of Use on behalf of the operator running the agent. Returns endpoints, an agent token, the fixed claim page URL, the expiry time and next_steps.

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": {
      "accepted_terms_version": "<accepted_terms_version>"
    },
    "name": "create_tenant"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNoOptional profile: Generic (default), Microsoft (Entra ID), or AzureAdB2C (one synthetic sign-in policy).
display_nameNoOptional display name of the tenant.
idempotency_keyNoStrongly recommended: a random secret of 32 to 128 characters from A-Z a-z 0-9 - _ (for example crypto.randomUUID()), generated once per intended tenant and kept secret like the agent token. Retrying with the same value and arguments, only if you never received the response, returns the same tenant instead of creating another.
accepted_terms_versionYesThe current Terms of Use version (see get_catalog), accepted on behalf of the operator running the agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries the whole disclosure burden. It does substantial work: it states the result is 'unverified', that it creates a demo client and test user, that it accepts the Terms of Use on the operator's behalf (a real consent consequence), and it enumerates what is returned. It omits authentication requirements, rate or quota limits, whether the agent token is returned only once, and what happens on failure.

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 opening with the verb, with each clause adding real information (unverified status, bundled demo client/user, terms acceptance, return payload). It is dense but not padded; splitting the return payload into its own sentence would improve scanability.

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 no output schema and no annotations, the description compensates well by enumerating the returned endpoints, agent token, claim page URL, expiry, and next_steps. However, for a tenant-provisioning mutation with four parameters it still leaves gaps around authorization/prerequisite context and failure behavior, so it is adequate rather than complete.

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?

Schema description coverage is 100%, so the schema already explains profile, display_name, idempotency_key, and accepted_terms_version in detail. The description adds meaning only for accepted_terms_version by clarifying that acceptance is made on behalf of the operator running the agent; the baseline 3 is exceeded slightly by that consent framing but the other three params are left entirely to the schema.

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 names a concrete verb (creates) and a concrete resource (an unverified HeyIdentity test tenant), and it goes further by listing the composite side effects: a working demo client and a test user. It does not explicitly say how this differs from siblings such as add_client/add_user or create_configuration, though the composite wording implies it bundles those steps.

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?

Use is only implied: an agent can infer that this is the bootstrap step that produces a tenant, token, and claim page, and that accepted_terms_version comes from get_catalog. There is no explicit when-to-use/when-not-to-use framing, no statement about prerequisites beyond terms acceptance, and no guidance about how many tenants one may create or when sibling add_* tools should be used instead.

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