Skip to main content
Glama

Send feedback

submit_feedback

Report a gap or problem in this Clerk MCP server so the Clerk team can fix it. Call it as soon as you find it, then continue the task: when none of these tools can do what the task needs (the most useful kind of report), when a tool error stops the task or a tool returns something wrong, when a tool or its documentation is confusing, or when the user asks you to report something. You do not need to ask the user first. Never include secrets, API keys, tokens, or personal data about end users.

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": {
      "kind": "<kind>",
      "task": "<task>",
      "description": "<description>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhat kind of problem: "missing" (no tool could do what the task needed), "broken" (a tool failed or returned something wrong), "confusing" (a tool or its documentation was unclear), or "idea" (a suggestion that would have helped).
taskYesA short phrase naming what the user asked you to do, such as "Add an organization switcher".
errorNoThe exact error you received, with any secrets removed.
impactNoHow the task went, if known: "blocked" (cannot finish), "worked_around" (finished another way), or "friction" (finished, but it was harder than it should be). Omit it when the task is still going.
operationNoName of the tool the problem is about, such as create_user. Omit it when no tool was involved.
suggestionNoWhat would have helped.
descriptionYesWhat you tried, including each tool call you made, and what went wrong or was confusing. Include both.

Output Schema

NameRequiredDescriptionDefault
receivedYes
feedback_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changed
    • removedInput schema / properties / attempted
      Removed value: -{
      -  "description": "The steps you took and the Clerk tool calls you made.",
      -  "maxLength": 4000,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "What you tried, including each tool call you made, and what went wrong or was confusing. Include both.",
      +  "maxLength": 4000,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / error
      Added value: +{
      +  "description": "The exact error you received, with any secrets removed.",
      +  "maxLength": 4000,
      +  "type": "string"
      +}
    • removedInput schema / properties / error_text
      Removed value: -{
      -  "description": "The exact error you received, with any secrets removed.",
      -  "maxLength": 4000,
      -  "type": "string"
      -}
    • removedInput schema / properties / goal
      Removed value: -{
      -  "description": "What the user asked you to accomplish.",
      -  "maxLength": 2000,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / impact
      Added value: +{
      +  "description": "How the task went, if known: \"blocked\" (cannot finish), \"worked_around\" (finished another way), or \"friction\" (finished, but it was harder than it should be). Omit it when the task is still going.",
      +  "enum": [
      +    "blocked",
      +    "worked_around",
      +    "friction"
      +  ],
      +  "type": "string"
      +}
    • removedInput schema / properties / issue
      Removed value: -{
      -  "description": "What went wrong or was confusing.",
      -  "maxLength": 4000,
      -  "minLength": 1,
      -  "type": "string"
      -}
    • addedInput schema / properties / kind
      Added value: +{
      +  "description": "What kind of problem: \"missing\" (no tool could do what the task needed), \"broken\" (a tool failed or returned something wrong), \"confusing\" (a tool or its documentation was unclear), or \"idea\" (a suggestion that would have helped).",
      +  "enum": [
      +    "missing",
      +    "broken",
      +    "confusing",
      +    "idea"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / operation
      Added value: +{
      +  "description": "Name of the tool the problem is about, such as create_user. Omit it when no tool was involved.",
      +  "maxLength": 1000,
      +  "type": "string"
      +}
    • removedInput schema / properties / outcome
      Removed value: -{
      -  "description": "How it ended: \"blocked\" (could not finish), \"worked_around\" (finished with a workaround), or \"succeeded_with_friction\" (finished but it was harder than it should be).",
      -  "enum": [
      -    "blocked",
      -    "worked_around",
      -    "succeeded_with_friction"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / task
      Added value: +{
      +  "description": "A short phrase naming what the user asked you to do, such as \"Add an organization switcher\".",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • removedInput schema / properties / tool_name
      Removed value: -{
      -  "description": "The Clerk MCP tool involved, if any.",
      -  "maxLength": 100,
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "goal",
      -  "attempted",
      -  "outcome",
      -  "issue"
      -]New value: +[
      +  "kind",
      +  "task",
      +  "description"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "feedback_id": {
      +      "type": "string"
      +    },
      +    "received": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "feedback_id",
      +    "received"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, openWorldHint=true, non-idempotent, non-destructive), but the description adds the key behavioral contract: submit as soon as the issue is found and continue the task, without pausing for user confirmation. It also imposes a data-handling rule (never include secrets, API keys, tokens, or end-user PII), which is genuine context not present in the annotations.

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?

The purpose is front-loaded in the first clause and every subsequent sentence carries distinct information (triggers, autonomy, privacy). The trigger list is a long comma-chained sentence, which slightly reduces scannability but does not waste words.

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 7-parameter submission tool with full schema coverage, an output schema, and annotations, the description supplies the remaining pieces an agent needs: when to fire, whether to ask first, and what must never be included. Nothing essential to correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the enum meanings for kind and impact are already fully documented, and the baseline would be 3. The description still adds value by signaling that the 'no tool could do it' case is 'the most useful kind of report' (steering toward kind=missing) and by specifying the redaction rule that applies to the error and description fields.

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?

The opening sentence gives a specific verb ('Report') and resource ('a gap or problem in this Clerk MCP server') plus the beneficiary ('so the Clerk team can fix it'). This clearly separates it from list_application_feedback, which reads as the retrieval counterpart.

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?

It enumerates concrete trigger conditions: no tool can do what the task needs, a tool error blocks the task, a tool returns wrong results, documentation is confusing, or the user asks. It also resolves the obvious ambiguity an agent would have by stating 'You do not need to ask the user first.'

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