Skip to main content
Glama

Set the form digest email and the site name

set_form_digest
DestructiveIdempotent

Change your form inbox's settings: the daily digest email to your owner (digest on or off: at most one email a day for all their forms, only while new entries arrive) and the site name its thank-you page shows visitors (site_name). Send either or both. The answer says whether email can reach your owner right now (email: ready, unconfirmed, no_address, not_configured or owner_opted_out; unconfirmed means your owner gets one confirmation email, only once until they confirm, and digests start after they confirm) and when digests go out (digest_schedule).

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "digest": true,
      "site_name": "Example Site",
      "instance_id": "frm_exampleexampleexample2"
    },
    "name": "set_form_digest"
  }
}

Input Schema

NameRequiredDescriptionDefault
digestNotrue: daily digest email on; false: off.
site_nameNoThe name of your site, shown as plain text on the thank-you page after a visitor sends the form: a plain name (no links or phone numbers), 1 to 60 characters once trimmed (maxLength 240 only caps the raw text). null clears it.
instance_idYesUtility instance id from buy or list_utilities.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / site_name / description
      Previous value: -"The name of your site, shown as plain text on the thank-you page after a visitor sends the form. null clears it."New value: +"The name of your site, shown as plain text on the thank-you page after a visitor sends the form: a plain name (no links or phone numbers), 1 to 60 characters once trimmed (maxLength 240 only caps the raw text). null clears it."
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "digest": true,
      +    "instance_id": "frm_exampleexampleexample2",
      +    "site_name": "Example Site"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  3. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  4. Changed2 schema fields changed
    • addedInput schema / properties / site_name
      Added value: +{
      +  "anyOf": [
      +    {
      +      "maxLength": 240,
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "The name of your site, shown as plain text on the thank-you page after a visitor sends the form. null clears it."
      +}
    • changedInput schema / required
      Previous value: -[
      -  "instance_id",
      -  "digest"
      -]New value: +[
      +  "instance_id"
      +]
  5. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / digest / description
      Added value: +"true: daily digest email on; false: off."
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds substantial context beyond them: the digest cadence ('at most one email a day ... only while new entries arrive'), the meaning of each email status value, and the confirmation-email flow. It does not explain why the operation is destructive (e.g., that null clears site_name or that turning digest off stops mail), leaving a small gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and relevant, but it is delivered as one long sentence with nested parentheticals that is hard to parse. Splitting the digest, site_name, and return-value explanations would improve readability without adding length.

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?

With no output schema, the description usefully documents the return values (email status enum and digest_schedule), and it covers both settable fields. It is nearly complete, missing only an explicit note on the destructive/clearing behavior.

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 baseline is 3, but the description adds real meaning: it explains what digest on/off does behaviorally and that site_name appears on the thank-you page, going beyond the schema's field-level text.

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 names a specific verb ('Change') and the exact resources ('form inbox's settings: the daily digest email ... and the site name'), and it distinguishes this from siblings like confirm_owner_email or get_email_check by focusing on setting rather than checking/confirming.

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?

'Send either or both' clarifies that partial updates are allowed, which is useful usage guidance. However, it never states when to prefer this over related tools such as confirm_owner_email or get_email_check, so the when-to-use context is only implied.

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.