Skip to main content
Glama

Clerk

by io.github.clerk
OverviewDiscussionsAdmin

Server Details

Access Clerk authentication docs, SDK snippets, and quickstart guides

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over 47 days
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL

TDQS

B3.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves a specific snippet, the other lists all snippets. No overlap in functionality or ambiguity.

Naming Consistency2/5

Naming is inconsistent: 'clerk_sdk_snippet' is a noun phrase without a verb, while 'list_clerk_sdk_snippets' follows a verb_noun pattern. Also mixes singular and plural forms, breaking predictability.

Tool Count3/5

With only 2 tools, the server feels thin but is arguably sufficient for a read-only snippet retrieval service. It falls in the borderline range for low tool counts.

Completeness4/5

The surface covers listing and fetching snippets, including tag filtering for discovery. No create/update/delete operations are expected for a static snippet repository, so the read-only coverage appears complete.

Available Tools

2 tools
clerk_sdk_snippetClerk SDK snippetBInspect

Get Clerk SDK code snippets and patterns.

ParametersJSON Schema
NameRequiredDescriptionDefault
slugNoSDK snippet slug (e.g. "use-user", "use-auth") OR bundle name (e.g. "b2b-saas", "organizations").b2b-saas

Output Schema

ParametersJSON Schema
NameRequiredDescription
textYesRequested Clerk SDK snippet or bundle in Markdown.

TDQS

B3.2/5.0
Behavior2/5

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

The annotations provide no helpful safety hints since all three hints are false, so the description carries the transparency burden. It only says 'get' and adds no context about side effects, authentication, rate limits, or the fact that a whole bundle may be returned rather than a single snippet.

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?

The description is a single, front-loaded sentence that immediately communicates the core action. It contains no filler or unnecessary detail, though it does repeat 'Clerk SDK' from the title.

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

Completeness4/5

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

For a low-complexity tool with one optional parameter, a detailed slug schema, and an output schema, the definition is mostly sufficient for invocation. The main gap is that it does not point the agent to list_clerk_sdk_snippets for discovering valid slugs, though the schema already covers the default value.

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?

The input schema already documents the 'slug' parameter thoroughly with examples of both snippet slugs and bundle names, so schema description coverage is 100%. The tool description adds no parameter-specific meaning beyond this, making the baseline score appropriate.

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 states a clear action ('Get') and a resource ('Clerk SDK code snippets and patterns'), so the basic purpose is understandable. However, it does not specify that a particular snippet or bundle is retrieved by slug, which leaves it less distinct from the sibling list_clerk_sdk_snippets.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool instead of list_clerk_sdk_snippets, or that the sibling should be used to discover available slugs. An agent must infer the intended usage entirely from the tool name and schema.

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

list_clerk_sdk_snippetsList Clerk SDK snippetsBInspect

List all available Clerk SDK snippets and bundles. Filter by tag to find specific functionality.

ParametersJSON Schema
NameRequiredDescriptionDefault
tagNoFilter snippets by tag (e.g. "auth", "organizations", "b2b", "billing")

Output Schema

ParametersJSON Schema
NameRequiredDescription
textYesAvailable Clerk SDK snippets and bundles in Markdown.

TDQS

B3.4/5.0
Behavior3/5

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

Annotations are all false, so the description carries the burden of behavioral disclosure. It states the tool lists snippets and bundles and can filter by tag, but doesn't disclose return format, pagination, or whether bundles are included by default. It adds some context beyond annotations but not rich behavioral detail.

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?

Two sentences, front-loaded with the main purpose and a clear filter instruction. No wasted words, though it could be slightly more specific about the relationship to the sibling tool.

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 simple list tool with one optional parameter and an output schema, the description is mostly complete. However, it doesn't clarify whether bundles are separate from snippets, how tags map to results, or any pagination/limits. The output schema exists, so return values are covered, but the tag filtering semantics could be clearer.

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 the schema already documents the tag parameter. The description adds the example tags and the filtering behavior, but doesn't add significant meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool lists all available Clerk SDK snippets and bundles, with a filter by tag. It distinguishes itself from the sibling tool clerk_sdk_snippet by focusing on listing rather than retrieving a single snippet, though it doesn't explicitly name the sibling.

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?

The description implies usage: use this tool to list snippets and filter by tag. It doesn't explicitly state when to use this tool versus clerk_sdk_snippet, but the listing vs. single-snippet distinction is inferable from the name and description.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • Changedclerk_sdk_snippet1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "text": {
+      "description": "Requested Clerk SDK snippet or bundle in Markdown.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}
    • Changedlist_clerk_sdk_snippets1 field changed
      • changedOutput schema / (root)
        Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "text": {
+      "description": "Available Clerk SDK snippets and bundles in Markdown.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "text"
+  ],
+  "type": "object"
+}
  2. 2 tool updates
    • Changedclerk_sdk_snippet2 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • removedInput schema / additionalProperties
        Removed value: -false
    • Changedlist_clerk_sdk_snippets2 fields changed
      • changedInput schema / $schema
        Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
      • removedInput schema / additionalProperties
        Removed value: -false
  3. 2 tool updates
    • First observedclerk_sdk_snippet
    • First observedlist_clerk_sdk_snippets

Related MCP Connectors

Related MCP Servers

  • DevDocs MCP Server

    elblanco2
    F
    license
    A
    quality
    D
    maintenance
    Provides access to 600+ documentation libraries from DevDocs.io including Python, JavaScript, React, Django, and more. Enables searching, browsing, and retrieving documentation content directly through Claude Desktop.
    5
    5
    -

  • BaaS-MCP

    mbaas-inc
    A
    license
    A
    quality
    D
    maintenance
    Enables interaction with AIApp BaaS authentication system through keyword-based document search and automatic generation of framework-specific client code. Supports React, Next.js, Vue, and Vanilla JS with TypeScript integration and automatic project ID injection.
    3
    24 npm
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources