Skip to main content
Glama

ADS Beast

prepare_client_report_send

Prepare generating the monthly report for a client and emailing it to the client's address on record. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "client_id": "<client_id>",
      "reason": "<reason>"
    },
    "name": "prepare_client_report_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonYesWhy, with numbers (shown to the approver).
client_idYes
send_emailNoSend by email (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds genuinely useful context beyond them: nothing external is mutated, the returned preview_id lives 15 minutes, is single use, and must be redeemed via execute_prepared_change. Mild tension with readOnlyHint=false ('changes nothing'), but storing an ephemeral preview token is a write, so this is scope description rather than a contradiction.

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?

Two tight sentences: the first gives purpose, the second gives the safety and redemption contract. Front-loaded and free of filler, with only a slightly awkward 'Prepare generating' opening.

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 prepare-step tool with no output schema, it covers what matters: what gets staged, that no external change occurs, the preview_id lifetime and single-use constraint, and the required follow-up call. Remaining gaps (what the preview contains, what reason is used for) are minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description confirms the emailing behavior ('to the client's address on record'), which clarifies how send_email behaves when omitted. It says nothing about client_id or the required reason field, so it matches rather than exceeds the schema's own documentation.

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?

States a specific verb (prepare), the exact resource (the monthly report for a client), and the side effect being staged (emailing it to the client's address on record). The follow-up tool is named, so an agent can distinguish this from the many other prepare_* siblings without opening the schema.

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?

The description makes the two-step contract explicit: this call stores a preview_id to show, then execute_prepared_change performs the action. It does not state when to skip this and act directly, but for a prepare/execute pair the workflow guidance is clear.

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.