Skip to main content
Glama
Sign In

SalesHookAI

by com.saleshookai
OverviewDiscussionsAdmin

Create custom document

createCustomDocument

Creates a freeform document (e.g. Leistungsverzeichnis, checklist, timesheet, short report) as a PDF and returns a one-time download link. By default the PDF carries the company letterhead; with documentData.noLetterhead set to true it is a neutral document without company data.

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": {
      "documentData": "<documentData>"
    },
    "name": "createCustomDocument"
  }
}

Input Schema

NameRequiredDescriptionDefault
documentDataYesDocument object: { title, subtitle?, letterText?, customerName?, customerCompany?, noLetterhead?: boolean, format?: "pdf" | "txt" | "md", blocks: [...] }. Block types: { type: "heading", text, level?: 1 | 2 }, { type: "paragraph", text }, { type: "table", columns: ["Col A", "Col B"], rows: [["a1", "b1"], ["a2", "b2"]], legend? }, { type: "divider" }. At least one block. Example: { title: "Checkliste Baustelle", blocks: [{ type: "heading", text: "Vor Ort" }, { type: "paragraph", text: "Wasser abstellen, Boden abdecken." }] }.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world creation. The description adds genuinely useful behavior beyond that: the result is a PDF with a one-time download link, and the letterhead is applied by default unless noLetterhead is true. It omits permission requirements, any size/block limits, and whether repeated calls create duplicate artifacts (relevant since idempotentHint is false).

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?

Two sentences, zero filler, and the most decision-relevant facts (what is produced, what is returned, letterhead default) are front-loaded. Nothing repeats the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single, fully documented nested parameter with no output schema, the description covers output form and the key letterhead toggle adequately. The one gap is that it states the document is created 'as a PDF' while the schema also allows format 'txt' and 'md', leaving a minor ambiguity an agent must resolve from the schema.

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 description coverage is 100%, so the schema already documents the nested documentData shape, block types, and the example. The description still adds meaning by explaining the default letterhead behavior and its opt-out semantics, which the schema only lists without stating the default.

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 names a specific verb (creates) and resource (freeform document), lists concrete document examples (Leistungsverzeichnis, checklist, timesheet, short report), and states the output (PDF plus one-time download link). It does not explicitly contrast itself with the entity-specific create* siblings, but the generic freeform scope makes the distinction largely self-evident.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The document-type examples imply when this tool is appropriate (ad-hoc/generic documents rather than structured business records), and the letterhead sentence gives a conditional usage choice via documentData.noLetterhead. However, there is no explicit when-not guidance, no mention of alternatives for structured documents, and no stated prerequisites.

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

All SalesHookAI 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