Skip to main content
Glama
deyikong

SendGrid MCP Server

by deyikong

Get Scopes

get_scopes

Retrieve available API key permission scopes to configure access levels for SendGrid email operations, ensuring proper authorization for marketing and transactional email tasks.

Instructions

Get available permission scopes for API keys

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the get_scopes tool by making an API request to retrieve available permission scopes from SendGrid and formatting the response as JSON.
    handler: async (): Promise<ToolResult> => {
      const result = await makeRequest("https://api.sendgrid.com/v3/scopes");
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    },
  • The schema/configuration for the get_scopes tool, defining its title and description.
    get_scopes: {
      config: {
        title: "Get Scopes",
        description: "Get available permission scopes for API keys",
      },
  • src/index.ts:21-22 (registration)
    Registration of all tools, including get_scopes, via server.registerTool in the MCP server setup.
    for (const [name, tool] of Object.entries(allTools)) {
      server.registerTool(name, tool.config as any, tool.handler as any);
  • Aggregation of all tools including miscTools (which contains get_scopes) into allTools for top-level registration.
    export const allTools = {
      ...automationTools,
      ...campaignTools,
      ...contactTools,
      ...mailTools,
      ...miscTools,
      ...statsTools,
      ...templateTools,
    };
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does without mentioning permissions needed, rate limits, response format, or other behavioral traits. This is inadequate for a tool with zero annotation coverage.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is front-loaded and appropriately sized for a simple tool.

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?

Given the tool has 0 parameters, no annotations, and no output schema, the description is minimally complete but lacks depth. It covers the basic purpose but doesn't address behavioral aspects or usage context, which could be important for an API scope tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, so no parameter information is needed. The description doesn't add param details, which is acceptable here, and it implies no inputs are required, aligning with the schema. Baseline is 4 for zero parameters.

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 states the verb 'Get' and the resource 'available permission scopes for API keys', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools, as none of the siblings appear to handle scopes directly, so the distinction is implicit rather than explicit.

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 provides no guidance on when to use this tool versus alternatives, such as which scenarios require checking scopes or if there are prerequisites. It lacks explicit context or exclusions, leaving usage unclear beyond the basic purpose.

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/deyikong/sendgrid-mcp'

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