Skip to main content
Glama

Enable the Native API

enable_native_api
Idempotent

Turn on an instance's Native API, which iOS and Android apps need to use Clerk. Returns the Native API settings, with api_enabled. Register the app first with create_ios_application or create_android_application. Enabling it again changes nothing. To turn it off, use the Clerk Dashboard.

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": {
      "application_id": "<application_id>",
      "instance": "<instance>"
    },
    "name": "enable_native_api"
  }
}

Input Schema

NameRequiredDescriptionDefault
instanceYesInstance to target: "development", "production", or a full instance ID (ins_…).
application_idYesClerk application ID (app_…).

Output Schema

NameRequiredDescriptionDefault
api_enabledYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the "enabling again changes nothing" sentence largely restates structured data. The genuine added value is the disclosure that this tool has no disable counterpart and that disabling must happen in the Clerk Dashboard, plus the return field api_enabled — behavior an agent could not infer from annotations alone.

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?

Four short sentences, verb first, with the prerequisite and the off-switch caveat each given their own clause. Nothing is redundant with the title, and no sentence could be deleted without losing a distinct fact.

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 mutation with a declared output schema, the description supplies everything an agent needs: what it does, what must exist first, that repeats are safe, and where the inverse operation lives. Return-value explanation is unnecessary because the output schema is present.

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 both parameters document their accepted formats ("development"/"production"/ins_… and app_…), so the schema carries the parameter burden. The description adds no format, defaulting, or validation detail beyond what the schema already states, which is the expected baseline here.

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?

Opens with a specific verb and resource ("Turn on an instance's Native API") and immediately scopes why it exists (iOS/Android apps using Clerk). It names the enabling prerequisites (create_ios_application / create_android_application), so an agent can distinguish it from the sibling tools that create apps rather than enable the API.

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?

Gives an explicit ordering constraint ("Register the app first with create_ios_application or create_android_application"), states the repeat-call behavior ("Enabling it again changes nothing"), and explicitly redirects the inverse operation out of band ("To turn it off, use the Clerk Dashboard"). When-to-use, prerequisite, and when-not-available are all covered.

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