Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Get Template

get_template
Read-onlyIdempotent

Get a template by name. The returned template token is accepted by 'render_template_preview', 'edit_template', 'get_template_content' and 'save_template'. Edits made with the token stay in a draft until 'save_template' stores them under the template's name.

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

Input Schema

NameRequiredDescriptionDefault
NameYesName of the template to get.

Output Schema

NameRequiredDescriptionDefault
TemplateTokenYesTemplate token accepted by 'render_template_preview', 'edit_template', 'get_template_content' and 'save_template'.
TemplateDataSchemaYesData schema inferred from the template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / TemplateToken / description
      Previous value: -"Template token accepted by 'render_template_preview', 'modify_template' and 'save_template'."New value: +"Template token accepted by 'render_template_preview', 'edit_template', 'get_template_content' and 'save_template'."
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond that: the returned token is a capability handle accepted by other tools, and edits via that token remain in a draft until save_template persists them. That lifecycle disclosure is the most valuable part of the definition.

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?

Three sentences, front-loaded with the core action, then the token contract, then the draft/save rule. Every sentence carries information. Slightly dense with quoted tool names but no filler.

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?

An output schema exists, so return values need not be explained, and the description still usefully characterizes the key returned artifact (the token) and its downstream contract. For a one-parameter read tool this is essentially complete; only discovery-of-names guidance is absent.

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 parameter 'Name' is already documented in the schema as 'Name of the template to get.' The description's 'by name' phrasing is consistent but adds no format, casing, or lookup guidance, so the schema carries the load and the baseline 3 applies.

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 and resource ('Get a template by name'), which cleanly separates it from list_templates and get_template_content. The follow-on sentences identify the token as the artifact this tool produces, so an agent knows exactly what it gets back.

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 names the four sibling tools that consume the returned token (render_template_preview, edit_template, get_template_content, save_template), which effectively routes the agent into the correct workflow. It stops short of stating the inverse (e.g., use list_templates to discover names first, or when to skip this tool entirely), so not a full 5.

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

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