Title94/100
Clerk SDK snippet
The title clearly communicates the tool’s action and subject. Keep it concise.
Description60/100
Get Clerk SDK code snippets and patterns.
Describe the concrete operation and its scope instead of restating the tool name.
Inputs95/100
Input documentation gives an agent enough context to populate the arguments.
slug
SDK snippet slug (e.g. "use-user", "use-auth") OR bundle name (e.g. "b2b-saas", "organizations").
Clear enough to supply this argument.
context
One sentence on what the user is trying to accomplish with this call. Used only for product analytics. Do not include names, email addresses, IDs, or secrets.
Clear enough to supply this argument.
Annotations100/100
All four behavior hints are declared.
{
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}Output schema88/100
The output schema explains the structured result.
View output schema
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "Requested Clerk SDK snippet or bundle in Markdown."
}
},
"additionalProperties": false
}