Skip to main content
Glama

HeyIdentity

create_configuration

Creates another configuration in the tenant from the starter content (a demo user and a demo client), with a name unique in the tenant and a profile. Prefer a separate client per environment in one configuration; create a configuration for a different profile or a separate set of users. A retry with the same name answers configuration_exists with the existing configuration instead of creating a second one.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe configuration's name, at most 200 characters and unique in the tenant ignoring case, e.g. staging.
profileNoOptional profile: Generic (default), Microsoft (Entra ID), or AzureAdB2C (one synthetic sign-in policy).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses the starter content, tenant-wide name uniqueness, and idempotent retry behavior returning configuration_exists with the existing configuration. It does not discuss authentication requirements or the successful response shape, so it is not fully exhaustive.

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?

Three tight sentences: core creation behavior first, selection guidance second, and retry edge case last. Nothing is repeated unnecessarily and the structure is front-loaded for quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter creation tool with no annotations or output schema, the description covers what is created, naming uniqueness, profile selection guidance, when to create a separate configuration, and idempotent retry behavior. It gives the agent enough to invoke the tool correctly without needing to infer hidden side effects.

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 coverage is 100%, so the schema already documents the name length/case-uniqueness rule and the profile options. The description restates uniqueness and profile context but adds no syntax or edge-case meaning beyond the schema, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Creates') and resource ('configuration in the tenant') and identifies the initial content (demo user and demo client) plus the required unique name and profile. This is more than a restatement of the tool name and lets an agent distinguish it from tenant-level or client-level creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly advises preferring a separate client per environment within one configuration and creating a new configuration only for a different profile or a separate set of users. That gives both an alternative pattern and the conditions for choosing this tool rather than leaving usage to inference.

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