Skip to main content
Glama
Sign In

Nextmail

by sh.nextmail
OverviewDiscussionsAdmin

Update connector

updateConnector
Destructive

Rename a connector, pause or resume it, or change its access. Send only what changes. paused true stops every use of it until paused false. access read limits the assistant to looking things up, and full also allows changes, each after approval.

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": {
      "id": "<id>"
    },
    "name": "updateConnector"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id of the connector, which starts with `cnr_`.
labelNoA name of your own for the connector, such as Sales Slack. Up to 80 characters.
accessNoWhat the assistant may do through it. `read` lets it look things up. `full` also lets it make changes, which it asks a person about first in chat and in tasks. Left out, it is `full`.
pausedNo`true` stops every use of the connector until it is resumed. `false` resumes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already signal a destructive mutation (readOnlyHint=false, destructiveHint=true). The description adds valuable context: paused true stops every use until false, and access read limits to lookups while full allows changes after approval. It doesn't cover permissions or error behavior, but adds substantial meaning beyond annotations.

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 three sentences, front-loaded with the actions, followed by a key usage note ('Send only what changes') and concise explanations of the paused and access semantics. Every sentence adds value without unnecessary length.

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?

Given four parameters, a destructive mutation, and no output schema, the description covers the essential behavioral details. It could mention authorization requirements or what happens to other settings, but it is largely complete for an update tool.

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?

With 100% schema description coverage, the schema already documents each parameter. The description restates the parameters' effects (rename, pause, access) but provides little extra semantic detail beyond the schema's own descriptions, so a 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 uses specific verbs (rename, pause/resume, change access) and the resource (connector), making it clear this tool updates a connector. It distinguishes from read-only siblings like getConnector or readConnector by listing the mutation actions.

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 when to use this tool (to rename, pause, resume, or change access) but does not explicitly name alternatives or when not to use it. 'Send only what changes' is a usage instruction for invocation, not for tool selection.

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

All Nextmail toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources