Skip to main content
Glama
ATOM00blue

Drin MCP Server

by ATOM00blue

list_template_gallery

Browse curated starter templates with subject, HTML/text, and sample data, and copy them to create new templates.

Instructions

List curated starter templates (subject/html/text + sample data) you can copy into a new template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
senderNoProduct/sender externalId sent as X-Drin-Sender. Required only for account-wide API keys; overrides the server's default sender.
Behavior2/5

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

With no annotations, the description carries full burden. It states it lists templates but does not disclose any behavioral traits such as read-only nature, authentication requirements, or potential side effects. Minimal transparency for a listing operation.

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?

A single, concise sentence that front-loads the key action and result. Every word contributes meaning without unnecessary elaboration.

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

Completeness3/5

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

For a simple listing tool with no output schema and missing annotations, the description covers the basic purpose but lacks details on return format, pagination, or safety. Adequate but not comprehensive.

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% for the single optional parameter 'sender', with a clear explanation in the schema. The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states it lists curated starter templates with specific content types (subject/html/text + sample data) and the action of copying into a new template. It distinguishes from sibling tool list_templates by specifying 'curated starter templates'.

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 use for getting starter templates to copy, but does not explicitly state when to use this tool versus alternatives like list_templates or create_template. No exclusion criteria or alternative options are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ATOM00blue/drin-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server