GoodSender

Get Template Content

get_template_content

Read-onlyIdempotent

Get current contents of a template including all pending changes made with 'edit_template' tool.

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": {
      "TemplateToken": "<TemplateToken>"
    },
    "name": "get_template_content"
  }
}

Input Schema

Name	Required	Description	Default
`TemplateToken`	Yes	Template token. Create with 'create_template_draft' or 'get_template' tools.

Output Schema

Name	Required	Description	Default
`Content`	Yes	Content of the template.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The description successfully discloses a critical behavioral trait: it captures draft data. This context is highly valuable as it defines the content returned as the most recent version, including unfinalized edits, which is a trait not explicitly covered by the structural hints.

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?

The description is extremely concise and efficiently front-loads the most important contextual information—the inclusion of pending changes—in the first clause.

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

Completeness5/5

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

Given that the function retrieves content, specifying that it includes pending changes provides the essential behavioral context required for the agent to determine if the tool is appropriate for its current task.

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?

Since the schema coverage is 100%, the baseline for parameter understanding is 3. The description doesn't add fundamental semantic meaning to the 'TemplateToken' itself beyond defining its retrieval purpose, which is covered by the schema and function name.

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 clearly identifies the resource ('template content') and its function ('Get current contents'). By explicitly mentioning it includes pending changes, it defines its specific scope and differentiates itself from a simple read tool.

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 mention of 'all pending changes made with 'edit_template' tool' serves as a strong guide for usage, indicating that this tool should be used when the agent needs the latest state of the template, even if it has uncommitted modifications.

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

All GoodSender tools Inspect

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.