Skip to main content
Glama

Remove a block rule

unblock
Destructive

Remove a block rule so the AI can read a table or column again. Portward asks the user to confirm; call only when the user requests it.

Instructions

Remove a block rule so the AI can read that table or column again. Portward asks the user to confirm it themselves; only call this when the user asks for it.

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": {
      "source": "<source>",
      "table": "<table>"
    },
    "name": "unblock"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYes
columnNo
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds the important behavioral nuance that user confirmation is handled by Portward rather than the caller. It does not say whether the removal is reversible or what happens to related rules for the same table/source, which keeps it short of a 5.

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

Conciseness4/5

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

Two tight sentences with the effect stated first and the usage restriction second; no filler. Slightly compressed, but every clause carries information.

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?

Covers purpose, the when-to-call gate, and confirmation handling for a small mutation tool with no output schema. It still leaves an agent guessing about the meaning of `source` and about the scope of an unspecified column, which matters for calling it correctly.

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%, so the description carries the full burden for source, table, and column. It only gestures at table and column ("that table or column") and says nothing about what `source` means or what a null column implies for scope.

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?

Names a specific verb and resource ("Remove a block rule") and states the concrete effect ("so the AI can read that table or column again"). This makes it unmistakably the inverse of the sibling `block` tool without needing to open either schema.

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?

Gives an explicit gate: only call this when the user asks for it, and notes that Portward handles the confirmation itself. That combination tells the agent both when to use it and when not to invoke it proactively.

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