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 with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP
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 available snippets. No overlap or ambiguity.

Naming Consistency5/5

Both tool names follow the same pattern: 'clerk_sdk_snippet' and 'list_clerk_sdk_snippets' - consistent verb_noun structure with clear pluralization.

Tool Count4/5

Only two tools, but they serve a narrow, focused purpose (snippet retrieval and listing). This is slightly thin but not unreasonable for a minimal reference server.

Completeness4/5

The server covers reading and listing snippets, which is typical for a reference library. Missing create/update/delete operations, but those may be intentionally omitted for a read-only snippet database.

Available Tools

2 tools
clerk_sdk_snippetClerk SDK snippetC
Read-only
Inspect

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

C2.5/5.0
Behavior2/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds no additional behavioral context—no mention of response format, filtering, or any constraints. It does not contradict annotations, but it also provides no extra insight beyond what the name implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no wasted words, but it is under-specified rather than concise in a helpful way. It omits usage guidance and differentiation, making it too minimal to be effective.

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 single-parameter read-only tool with an output schema, the schema covers the parameter semantics well. However, the description leaves gaps around how to select a slug and when to use this tool versus the sibling, so completeness is only marginal.

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 schema already fully documents the single parameter (slug) with examples and a clear description, achieving 100% coverage. The description adds nothing beyond the schema's parameter documentation, so the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description states a specific verb and resource ('Get Clerk SDK code snippets and patterns'), but it does not differentiate from the sibling tool list_clerk_sdk_snippets. It is not a tautology, but it is vague about what distinguishes this tool from listing 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 versus list_clerk_sdk_snippets. The description lacks any contextual cues, alternative routing, or exclusions, so an agent cannot determine the right tool for a given situation.

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 snippetsA
Read-only
Inspect

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

A3.7/5.0
Behavior3/5

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

Annotations already indicate readOnly and non-destructive behavior, so the description does not need to repeat that. It adds no extra behavioral context such as return format, pagination, or side effects beyond the basic listing and filtering.

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 succinct, consisting of two short sentences that efficiently convey the core function and the optional filter. No redundant information or verbose phrasing.

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 read-only listing tool with one optional parameter and no output schema, the description provides sufficient context to understand its purpose and basic usage. No additional details are needed for correct invocation.

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 single parameter 'tag' is fully documented in the schema with examples. The description merely echoes 'filter by tag' without adding new parameter-specific details, so it adds minimal value beyond the schema coverage.

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 it lists all Clerk SDK snippets and bundles, with an optional tag filter. It distinguishes the plural listing operation from the singular sibling 'clerk_sdk_snippet' implicitly, but does not explicitly name or contrast the alternative.

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 explains what the tool does but provides no explicit guidance on when to prefer this over the sibling tool for retrieving a single snippet. The filter example is helpful but does not cover use-case scenarios or limitations.

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
    41
    MIT
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources