Skip to main content
Glama

Send feedback to Clera

sendFeedback
Destructive

Send a note from the user to the Clera team through Slack, together with their name, email and company: a bug, a confusing tool, something Clera cannot do yet, or praise. Use it when the user asks to pass something on, or when they hit a problem and agree to report it; tell them what will be sent first. Include only the details needed to explain the issue. One call per distinct issue. The team reads every note; nothing comes back to relay.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "sentiment": "<sentiment>",
      "category": "<category>",
      "text": "<text>"
    },
    "name": "sendFeedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesWhat happened, plain and specific, in your own words: what the user was trying to do and what went wrong or right. Name the tools and errors involved; quote the user only when the exact wording matters. One issue per call; send several calls for several issues rather than ranking them.
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
categoryYesbug: a tool errored or returned wrong data. confusing_ux: the user did not understand what a tool did or how to use it. missing_feature: the user asked for something Clera cannot do. slow_or_broken: a real request stalled or silently failed. candidate_quality: the candidates themselves disappointed. praise: something worked well and the user reacted to it. other: none of the above.
toolNameNoThe specific Clera tool involved, when there is one. Omit for general product feedback.
sentimentYesThe user's state right now, as you read it. Use neutral only when there is truly no signal either way.

Output Schema

NameRequiredDescriptionDefault
recordedYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only flag destructive/openWorld/non-idempotent; the description adds the destination (Slack), the audience (the team reads every note), and the critical outcome that nothing comes back to relay. It also discloses a privacy trait the annotations do not cover: inputs and results are privately recorded for usage tracking and support.

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?

Front-loaded with the core action and destination, then triggers, then constraints, then the privacy disclosure. Dense with little filler, though the parenthetical list of issue types slightly overlaps the category enum in the schema and the final privacy sentence reads as appended rather than integrated.

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?

An output schema exists, so return values need not be described, yet the definition still closes the loop with 'nothing comes back to relay' — the one thing an agent would otherwise guess wrong about. Consent handling, privacy, granularity, and content guidance are all present for a 5-parameter outbound-write tool.

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 definitions already carry most parameter meaning and the baseline would be 3. The description still earns above baseline by constraining the free-text field ('include only the details needed', 'one call per distinct issue') and by stating that the user's name/email/company accompany the note, which is context the schema does not show.

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?

Specific verb and resource: 'Send a note from the user to the Clera team through Slack', with the payload channels (name, email, company) and the accepted subject matter (bug, confusing tool, missing capability, praise) spelled out. An agent can tell immediately this is the escalation/feedback channel and not any of the recruiting siblings.

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?

Gives the trigger conditions explicitly ('when the user asks to pass something on, or when they hit a problem and agree to report it'), adds a consent precondition ('tell them what will be sent first'), and a batching rule ('One call per distinct issue'). That is when-to-use plus how-to-scope, which is the full job for a single-purpose tool.

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