Skip to main content
Glama
Sign In
SendGrid MCP Server

SendGrid MCP Server

by deyikong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Sender

create_sender

Set up a verified sender identity for your emails. Provide sender details, reply-to, and physical address to enable reliable delivery and compliance.

Instructions

Create a new sender identity

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": {
      "nickname": "<nickname>",
      "from": "<from>",
      "reply_to": "<reply_to>",
      "address": "<address>",
      "city": "<city>",
      "state": "<state>",
      "zip": "<zip>",
      "country": "<country>"
    },
    "name": "create_sender"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesZIP code
cityYesCity
fromYes
stateYesState
addressYesStreet address
countryYesCountry
nicknameYesNickname for the sender
reply_toYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / from / additionalProperties
      Removed value: -false
    • removedInput schema / properties / reply_to / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations are limited to readOnlyHint=false and destructiveHint=false, so the description carries the burden of behavioral disclosure, but 'Create a new sender identity' adds nothing. An agent learns nothing about whether duplicate nicknames are rejected, whether sender identities require verification before use, whether the operation is idempotent (idempotentHint=false), or what side effects occur. No contradiction: the write action is consistent with readOnlyHint=false.

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?

A single six-word sentence with no wasted words, front-loaded with the action verb. However, for a tool with 8 required parameters — including two nested objects — and no output schema, this brevity is arguably under-specification rather than disciplined conciseness. It earns high marks for economy but not for appropriate sizing.

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

Completeness2/5

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

The tool is non-trivial: 8 required parameters, nested from/reply_to objects, no output schema, and no idempotence guarantee. The description does not explain what the tool returns on success, how failures surface, whether duplicate senders are allowed, or how the created identity relates to send_mail. There is no output schema to fill this gap, so the description is materially incomplete.

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 75%, near the threshold where the schema carries the explanatory load. The properties all have short descriptions ('ZIP code', 'City', 'Nickname for the sender'), though most are tautological. The description's 'sender identity' phrasing gently hints that the assembled fields (from, reply_to, postal address) form an identity, but it adds little meaning beyond the schema itself.

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 states a specific verb and resource: 'Create a new sender identity.' The purpose is unambiguous and the verb distinguishes it from the related siblings list_senders and delete_sender. However, it is very close to restating the title 'Create Sender' — the only added semantic is the word 'identity' — and it provides no detail about what constitutes a sender identity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives zero guidance on when to use this tool versus alternatives. With over 50 siblings including list_senders and delete_sender, and adjacent tools like create_email_list and create_contact, an agent receives no signal about the sender-identity use case or when not to call this tool. It is not misleading, but it provides no usage direction.

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

Deploy Server

Other Tools