Skip to main content
Glama
Sign In

SendIt

by io.github.Shree-git
OverviewDiscussionsAdmin

Connect Platform

connect_platform
Read-onlyIdempotent

Connect a platform dynamically by platform ID. Returns OAuth URL, webhook setup details, or credential form contract depending on the platform auth method.

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": {
      "platform": "<platform>"
    },
    "name": "connect_platform"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformYesPlatform ID to connect

Output Schema

NameRequiredDescriptionDefault
noteNo
setupNo
authUrlNo
isErrorNo
platformNo
usernameNo
connectedNo
errorMessageNo
alreadyConnectedNo
followUpSuggestionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "alreadyConnected": {
+      "type": "boolean"
+    },
+    "authUrl": {
+      "type": "string"
+    },
+    "connected": {
+      "type": "boolean"
+    },
+    "errorMessage": {
+      "type": "string"
+    },
+    "followUpSuggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "isError": {
+      "type": "boolean"
+    },
+    "note": {
+      "type": "string"
+    },
+    "platform": {
+      "enum": [
+        "x",
+        "linkedin",
+        "linkedin-page",
+        "facebook",
+        "instagram",
+        "threads",
+        "bluesky",
+        "mastodon",
+        "nostr",
+        "youtube",
+        "tiktok",
+        "lemmy",
+        "discord",
+        "slack",
+        "telegram",
+        "pinterest",
+        "dribbble",
+        "devto",
+        "hashnode",
+        "gmb",
+        "whop",
+        "producthunt"
+      ],
+      "type": "string"
+    },
+    "setup": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "username": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations by explaining that the output depends on the platform's auth method. This aligns with the readOnlyHint (it returns setup info rather than performing the connection) and clarifies the tool's side-effect-free nature.

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 two sentences, front-loaded with the action, and wastes no words. It delivers purpose and output context efficiently.

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?

The description covers the essential purpose, parameter, and output variability, and an output schema supplies return details. However, it omits guidance on choosing between this and the many dedicated connect_* tools, leaving some ambiguity in a crowded tool landscape.

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?

Schema coverage is 100%, so the platform enum is already documented. The description adds meaning by indicating that the parameter value affects the output contract (OAuth URL vs webhook vs credentials), which helps the agent anticipate behavior.

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 the tool connects a platform by ID and specifies the three possible return types (OAuth URL, webhook setup details, or credential form contract). This distinguishes it from sibling connect_* tools by emphasizing dynamic selection based on platform ID.

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 a generic dynamic connector ('dynamically by platform ID') but does not explicitly state when to use it over dedicated connect_* tools. No exclusions or alternatives are provided, so the agent must infer from the sibling list.

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

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