Skip to main content
Glama

ClauseAI

by io.github.wasauce
OverviewDiscussionsAdmin

List templates

list_templates
Read-onlyIdempotent

Use this when the user wants a startup legal document and you need to choose a template such as an NDA, MSA, DPA, privacy policy, terms of use, cookie notice, offer letter, advisor agreement, or business associate agreement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
templatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / description
      Added value: +"Templates the user can draft."
    • removedOutput schema / properties / result
      Removed value: -{
-  "items": {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  "type": "array"
-}
    • addedOutput schema / properties / templates
      Added value: +{
+  "items": {
+    "description": "One template in the public catalog.",
+    "properties": {
+      "category": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "field_count": {
+        "type": "integer"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "source_url": {
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      },
+      "when_needed": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "slug",
+      "title",
+      "category",
+      "description",
+      "when_needed",
+      "source_url",
+      "field_count"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "templates"
+]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is fully covered by structured data. The description adds domain context but nothing behavioral beyond that — no note on whether the list is static or dynamic, or how it relates to subsequent generation. With annotations carrying the safety profile, a 3 is appropriate.

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?

A single sentence that front-loads the usage condition before the template enumeration. The long list of document types is the only slightly padded element, though it does usefully scope the domain.

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 zero-parameter, read-only list tool with an output schema available to describe returns, the description supplies the one thing an agent needs: when this lookup is the right call. Nothing essential 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?

The tool takes zero parameters, so there is no parameter semantics for the description to explain. Baseline 4 applies; no gaps in this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description frames the tool as the one to reach for when selecting among startup legal templates and enumerates concrete examples (NDA, MSA, DPA, privacy policy, etc.), which makes the resource specific. It never states outright that the tool returns the available template list, so the verb is inferred from the name rather than declared in the text.

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 a clear triggering condition — the user wants a startup legal document and a template must be chosen — which implies this is the pre-generation lookup step. It does not name the sibling alternatives (e.g. generate_document, get_template_fields) or explicitly state that generation should follow, so routing is only implied.

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