Cursor
Grok Bot
Grok
MuseTitle54/100
Not provided
The title clearly communicates the tool’s action and subject. Keep it concise.
Description83/100
Submit explicit user-approved feedback to the Langfuse team. Before calling, ask permission and show the exact payload. If the user wants a reply, ask them to include their email address in the feedback text; only use an address they explicitly provide and show it in the exact payload preview. Do not include secrets, credentials, customer/project data, trace payloads, or unrelated context; the only contact detail to include is an explicitly provided reply email.
The description explains the capability, when to use it, and what to expect.
Inputs35/100
2 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.
targetType
Category of the thing the feedback is about.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
target
The specific instance within targetType: the skill name, MCP tool name, CLI command, API endpoint path, or docs page path (e.g. 'queryMetrics', '/docs/mcp'). An identifier, not a sentence.
Clear enough to supply this argument.
feedback
Not provided
Missing description. Explain what this value means and how to supply it.
goal
Not provided
Missing description. Explain what this value means and how to supply it.
referenceUrl
Not provided
Missing description. Explain what this value means and how to supply it.
Annotations0/100
Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.
Not declared
Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared