Skip to main content
Glama
Sign In

EmailFig

by com.emailfig
OverviewDiscussionsAdmin

Get template

get_template
Read-onlyIdempotent

One template's content. A drag and drop template returns its design (blocks and settings), which create_campaign_draft takes as body.blocks; any other template returns its HTML.

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": {
      "id": "<id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe template's id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the bar is lower and this description clears it by disclosing conditional output behavior: DnD templates yield design blocks and settings, all others yield HTML. That is information an agent cannot obtain from the annotations. It omits failure behavior for an unknown id and the approximate size/shape of the HTML payload.

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 waste, and the primary statement of what is returned is front-loaded before the conditional detail. The clause naming create_campaign_draft.body.blocks earns its space by linking the output to a concrete consumer.

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 must characterize return values, and it does so conditionally and accurately for the two template families. Missing only edge-case completeness (unknown id, empty design) for a one-parameter read tool.

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 description coverage is 100% and the single id parameter is documented as "The template's id", so baseline is 3. The description adds no syntax, format, or sourcing hint (e.g., where to obtain a valid id) beyond the schema.

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?

"One template's content" names the resource and what is returned, and the second sentence distinguishes two return shapes (design blocks/settings vs HTML) by template type. It is specific enough to separate this from list_templates and render_email_preview, though the retrieval verb is only implied by the name rather than stated.

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 description implies when the output is useful by tying drag-and-drop results to create_campaign_draft's body.blocks, which is real routing guidance. It gives no explicit when-to-use versus list_templates (to find the id) or render_email_preview, and no statement about preconditions such as the id needing to come from a list call.

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

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