Skip to main content
Glama
Sign In

hedwigai

by com.hedwigai
OverviewDiscussionsAdmin

Email a workbook to its members

email_workbook
Destructive

Sends the workbook, as last saved, to its members (configure_workbook's members), or to those of them named in send_to, with a link that opens it. Mail cannot be taken back: confirm who it goes to with the user first. With preview true it only says who it would go to.

Input Schema

NameRequiredDescriptionDefault
contextNoExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
previewNoOnly say who it would go to; send nothing.
send_toNoMembers' emails to send to. Omit for all of them. An address that is not a member is not mailed.
workbookYesThe workbook id.
llm_modelNoThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint, openWorldHint and non-idempotence; the description adds real value beyond them by stating mail cannot be recalled, that the last-saved version is what gets sent, and that non-member addresses are silently not mailed. Missing only permission/auth prerequisites for sending.

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?

Three tight sentences, each earning its place: what it does, the irreversibility warning, and the preview mode. The scoping phrase is front-loaded where an agent will read it first.

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 5-parameter mutation tool with full schema coverage and no output schema, the description covers recipients, versioning, irreversibility and dry-run behavior. It omits what a successful send returns (confirmation list, message ids), which would have made it fully complete.

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 100%, so this is a baseline 3. The description reinforces `preview` and `send_to` semantics but largely restates what the schema already documents (the non-member no-mail rule appears in both places) and adds no format or syntax detail for `workbook` or `context`.

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+resource ('Sends the workbook... to its members') plus the resolution rules for recipients and the 'as last saved' version qualifier. The members-only scoping implicitly separates it from share_workbook, so an agent can pick between them without opening either 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?

Gives clear operating context — confirm recipients with the user first, and use `preview` to dry-run. It stops short of naming an explicit alternative (e.g. share_workbook for granting access rather than mailing), so it is strong but not a full when/when-not map.

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

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