Skip to main content
Glama

ClauseAI

by io.github.wasauce
OverviewDiscussionsAdmin

Send feedback

send_feedback

Use this when a template lacks a field or clause the user needs, no template fits the request, a tool result was wrong, or the user wants to tell the ClauseAI team something. The message goes to the ClauseAI operator. Do not include document text or personal details, except an email or phone number the user offers for a reply.

Input Schema

NameRequiredDescriptionDefault
slugNoTemplate slug the feedback is about, if any.
emailNoOptional email address for a reply. Only pass one the user gave you.
phoneNoOptional phone number for a reply. Only pass one the user gave you.
messageYesWhat you were trying to do and what was wrong or missing. Up to 4000 characters.
categoryNobug, missing_field, template_request, or other.other

Output Schema

NameRequiredDescriptionDefault
detailYes
statusYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / email / description
      Previous value: -"Optional address for a reply. Only pass one the user gave you."New value: +"Optional email address for a reply. Only pass one the user\ngave you."
    • addedInput schema / properties / phone
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional phone number for a reply. Only pass one the user\ngave you."
+}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations, the description usefully discloses that the message goes to the ClauseAI operator and that document text or personal details should not be included except user-provided reply contact details. This adds meaningful context for a write/open-world operation, though it does not discuss retention or confirmation behavior.

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?

The description is two sentences and front-loads the usage conditions before stating the destination and privacy constraint. Every sentence adds useful information without repetition.

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?

The tool has an output schema and annotations covering its write and open-world nature, so return values and safety traits are already documented. The description fills the remaining gaps by explaining when to use it, where the feedback goes, and what must be excluded.

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 schema already documents all five parameters. The description still adds value by constraining what may go into the feedback message and by clarifying that reply contact details should only be included when the user offers them.

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 description makes clear that this tool sends feedback to the ClauseAI operator, and it lists specific triggering situations such as a missing template field or an incorrect tool result. This distinguishes it from sibling tools like generate_document and list_templates, which handle document generation and template discovery.

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?

It gives explicit when-to-use conditions: when a template lacks a needed field or clause, no template fits, a tool result was wrong, or the user wants to tell the ClauseAI team something. It also includes privacy guidance about what not to include, though it does not explicitly state when not to use the tool or name alternative paths.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ClauseAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources