Kivel

email_inbox_rules

DestructiveIdempotent

Read or replace inbound and outbound inbox address rules. Only a signed-in workspace owner or admin can replace rules or change requireApproval. Missing fields reset to their defaults. Inbound rules check header and envelope senders.

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": "email_inbox_rules"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Resource UUID.
`rules`	No	Optional replacement with inboundAllow, inboundBlock, outboundAllow and outboundBlock arrays.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the annotations, it discloses the authorization requirement, warns that missing fields reset to their defaults, and explains that inbound rules check both header and envelope senders. These details clarify permission failures, destructive reset behavior, and matching semantics, with no conflict against the idempotent or destructive hints.

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?

Four compact sentences front-load the purpose and then cover permissions, reset behavior, and sender matching. Every sentence contributes operational information with no filler or unnecessary repetition.

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?

For a dual read/destructive-replace tool with a nested object and no output schema, the description covers the principal authorization and replacement risks. It remains incomplete about the read response, allowed rule-entry representation, and actual defaults, so it is not fully comprehensive.

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?

The schema already identifies id and the optional replacement arrays, but the description adds omitted-field reset behavior, the privileged requireApproval field, and inbound header/envelope matching. It does not define individual rule-entry syntax or the concrete default values.

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 opening sentence gives both operations (“Read or replace”) and the exact resource (“inbound and outbound inbox address rules”). This distinguishes it from sibling tools for inbox creation, threads, attachments, and sending without relying on the tool name.

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

Usage Guidelines4/5

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

It provides clear read-versus-replace context and states that only a signed-in workspace owner or admin can replace rules or change requireApproval. It does not provide explicit when-not-to-use guidance or name an alternative, so it stops short of a 5.

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

All Kivel tools Inspect

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.