Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Create pod

create_pod

Creates a new pod (tenant) to establish an isolated workspace for permission-scoped email inbox operations managed by AI agents.

Instructions

Create a new pod (tenant).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_pod"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world, non-destructive mutation, so the safety profile is covered externally. The description adds only the pod=tenant gloss and says nothing about side effects, whether repeated calls create duplicate tenants, or what happens on name collision.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Six words with zero filler and the key term front-loaded, which is good. But brevity here comes at the cost of substance rather than being maximally economical with information.

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?

For a low-complexity one-parameter tool this is close, but with 0% schema coverage and no output schema, the definition leaves the agent unsure whether name is required and what the created pod looks like (id, domain). A sentence or two more would make it callable with confidence.

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

Parameters2/5

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

Schema description coverage is 0% for the single "name" parameter, so the description must carry the burden and does not: it never says what name means, whether it is optional (required list is empty), what format is expected, or what happens if omitted.

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?

States a specific verb (create) and resource (pod), and the parenthetical "(tenant)" disambiguates a domain-specific term. It does not explicitly contrast with siblings like delete_pod or get_pod, but the verb already separates it from read/delete operations.

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?

No when-to-use guidance at all: nothing about prerequisites (e.g. whether a domain must exist first), quota/tenant limits, or when to prefer an alternative creation tool. The agent must infer everything from the name.

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