Skip to main content
Glama

Clerk SDK snippet

clerk_sdk_snippet
Read-onlyIdempotent

Return one Clerk SDK snippet, or a bundle of related snippets, as a Markdown guide with code examples. An unknown slug returns the available snippets and bundles instead. Find slugs with list_clerk_sdk_snippets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "clerk_sdk_snippet"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
textYesRequested Clerk SDK snippet or bundle in Markdown.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema 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"
      +}
  2. Changed2 schema 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. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, not destructive, closed-world), so the description focuses on behavior: the return shape is a Markdown guide and an invalid slug degrades gracefully by returning available snippets and bundles. That fallback-on-error behavior is genuinely useful context not encoded in annotations or schema.

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 short sentences ordered by importance: what is returned, what happens on bad input, then how to discover slugs. No redundant restatement of the name or 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 single-parameter read with a full output schema and complete annotations, the description covers purpose, format, error fallback, and slug discovery. The main omission is the default value when slug is omitted, which could surprise an agent expecting a required lookup.

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% and the slug property already explains that it accepts either a snippet slug or a bundle name with examples, so the description adds little parameter meaning. It notably omits that the parameter is optional with a default of "b2b-saas", meaning an omitted slug silently resolves to a bundle.

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?

States a specific verb and resource ("Return one Clerk SDK snippet, or a bundle") plus the output format ("Markdown guide with code examples"), which is exactly the distinction an agent needs. It also implicitly separates itself from the listing sibling by naming list_clerk_sdk_snippets as the discovery path.

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

Usage Guidelines4/5

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

Gives concrete routing guidance: use list_clerk_sdk_snippets to find slugs, and expect a fallback listing when the slug is unknown. It does not explain when to request a single snippet versus a bundle beyond what the schema's examples imply, so a small gap remains.

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