@beyondidentity/mcp

Official

Overview Schema Source Related Servers Discussions Admin

create_binding_job

Provision a new passkey for a user by starting a credential binding job. Specify the user_id and delivery method; the binding link is sent to the user or returned directly.

Instructions

Create a credential binding job to provision a new passkey for a user. Specify the user_id and delivery method. The binding link is sent to the user or returned directly depending on the delivery method. Use list_users to find the user_id first.

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

Input Schema

Name	Required	Description	Default
`binding_job`	Yes	A binding job tracks the process of binding a new credential for a user.
`ttl_seconds`	No	Number of seconds until the binding job expires. This must be between 1 minute (60 seconds) and 15 minutes (900 seconds). This field is used only if the `expire_time` on the requested binding job is u

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Sep 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does usefully explain that the binding link is delivered via the chosen method (sent to the user or returned directly), but omits permission/auth requirements, what happens if the user already has a credential, and any idempotency or failure behavior.

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?

Three tightly written sentences with the core action front-loaded and the lookup hint placed last. Nothing is wasted, though it is brief enough that a little more detail would not have hurt.

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 mutation tool with no annotations and no output schema, the description covers the basic flow but leaves notable gaps: response shape (since no output schema exists, it should ideally describe what the caller receives), the 15-minute short-code expiry surfaced in the schema, and required authority to create a binding for another user.

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 user_id, delivery_method, and ttl_seconds are already well documented. The description only restates that user_id and delivery method must be specified, adding no format or constraint detail beyond 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?

States a specific verb and resource ('Create a credential binding job') and adds the outcome ('provision a new passkey for a user'), which cleanly separates it from the read-only get_binding_job sibling. It stops short of explicitly differentiating from other creation tools, but the purpose is unambiguous.

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?

Provides ordering guidance ('Use list_users to find the user_id first') and notes the delivery method determines how the link reaches the user. However, it offers no when-not conditions, prerequisites (permissions/issuer identity), or guidance on choosing between delivery paths beyond noting they exist.

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