Skip to main content
Glama
Sign In
SuprSend MCP Server - deprecated

SuprSend MCP Server - deprecated

by suprsend
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
Go

upsert_suprsend_tenant

Destructive

Create or update a tenant (sub-account) for multi-tenant SaaS apps. Merge tenant properties like branding, timezone, and contact info.

Instructions

Create a new tenant or update an existing tenant's properties. Tenants are sub-accounts of a workspace, used to model end-customers in multi-tenant SaaS apps.

tenant_properties is merged with existing — not replaced. Pass only the fields you want to change. Common fields include name, branding URLs, and contact info.

When NOT to use:

  • For preference defaults — use update_suprsend_tenant_default_preference.

  • For users / objects within a tenant — use upsert_suprsend_user / upsert_suprsend_object.

Returns: the updated tenant on success.

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": {
      "tenant_id": "<tenant_id>"
    },
    "name": "upsert_suprsend_tenant"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenant_idYesThe tenant_id of the tenant to upsert.
workspaceNoSuprSend workspace to get the tenant from.
tenant_propertiesNoThe properties to upsert for the tenant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0-beta.1

TDQS

A4.6/5.0
Behavior4/5

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

Annotations indicate destructiveHint=true, and the description confirms mutation (create/update). It adds value beyond annotations by stating tenant_properties is merged (not replaced) and that the updated tenant is returned. No contradictions.

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?

Description is front-loaded with the main action, then provides merge behavior, usage exclusions, and return value. Every sentence is valuable and well-structured, with no redundancy.

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?

Covers purpose, merge behavior, usage exclusions, and return value. Missing details on error cases or rate limits, but given annotations and schema richness, it is fairly complete. Output schema would help but is absent.

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% with descriptions for all parameters. The description adds the merging behavior for tenant_properties, which is not in the schema. This extra detail justifies a score above baseline 3.

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 explicitly states the tool creates or updates a tenant, which is a specific verb+resource. It distinguishes from siblings by noting when not to use it (preference defaults and user/object operations).

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

Usage Guidelines5/5

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

Provides explicit 'When NOT to use' section with alternative tool names (update_suprsend_tenant_default_preference, upsert_suprsend_user, upsert_suprsend_object). Also explains merging behavior for tenant_properties, guiding partial updates.

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