Skip to main content
Glama
Pombus MCP Server

Pombus MCP Server

Official

Add allow/block entry

create_list_entry
Idempotent

Add an email address to a specific inbox's allow or block list to control which senders are permitted or restricted.

Instructions

Add an address to an inbox's allow or block list.

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": {
      "inbox_id": "<inbox_id>",
      "direction": "<direction>",
      "list_type": "<list_type>",
      "address": "<address>"
    },
    "name": "create_list_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYes
inbox_idYesAn inbox id previously returned by list_inboxes. The server rejects any id outside this key's scope.
directionYes
list_typeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=true, so the safety and repeat-call profile is covered by structured data. The description adds only the notion that the entry belongs to a specific inbox — it does not say what happens if the address is already listed or how address formats are validated.

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?

One front-loaded sentence with no filler or repetition of the title. Every word carries content and there is nothing to trim.

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?

With four required parameters, 25% schema coverage and no output schema, the description should carry more of the burden. Purpose and target collection are clear, but direction and list_type value domains, plus behavior on duplicate entries, are left to guesswork.

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?

Schema description coverage is 25% (only inbox_id is documented), so extra meaning is needed. The description implicitly clarifies that address is the value being inserted and that list_type selects between allow and block, but it says nothing about direction, which is a required enum-less string left fully opaque.

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 pairs a specific verb ("Add") with a specific resource (an address) and states the two target collections (allow or block list), so the agent knows exactly what is created. It does not name a sibling such as list_list_entries or delete_list_entry, but the purpose is unambiguous on its own.

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?

There is no when-to-use guidance: nothing says when to choose allow versus block, when this should be used instead of list_list_entries or delete_list_entry, or what preconditions (e.g. an existing inbox) the call requires. Usage must be inferred entirely from the verb.

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