Skip to main content
Glama
Sign In
ThumbGate

ThumbGate

by IgorGanapolsky
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Satisfy Gate

satisfy_gate
Destructive

Satisfy a specified gate condition by submitting evidence and optional structured reasoning, storing the premise-evidence-conclusion chain in the audit trail for 5 minutes.

Instructions

Satisfy a gate condition with optional structured reasoning. Evidence is stored with a 5-minute TTL. When structuredReasoning is provided, the premise/evidence/conclusion chain is stored in the audit trail.

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": {
      "gate": "<gate>"
    },
    "name": "satisfy_gate"
  }
}

Input Schema

NameRequiredDescriptionDefault
gateYesGate condition ID to satisfy (e.g., pr_threads_checked)
evidenceNoEvidence text (e.g., "0 unresolved threads")
structuredReasoningNoStructured pre-gate reasoning: state premises, trace evidence, assess risk, derive conclusion before unlocking.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.23.1
  2. Removedv1.21.2
  3. Changed1 schema field changedv1.16.9
    • addedInput schema / properties / structuredReasoning
      Added value: +{
+  "description": "Structured pre-gate reasoning: state premises, trace evidence, assess risk, derive conclusion before unlocking.",
+  "properties": {
+    "conclusion": {
+      "description": "Based on evidence, should I proceed? Yes/No with justification.",
+      "type": "string"
+    },
+    "evidence": {
+      "description": "What specific, verifiable evidence supports this action?",
+      "type": "string"
+    },
+    "premise": {
+      "description": "What am I trying to do and why?",
+      "type": "string"
+    },
+    "risk": {
+      "description": "What could go wrong if this action proceeds?",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  4. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate destructiveHint=true, and description adds behavioral traits: evidence stored with 5-minute TTL, structured reasoning chained in audit trail. This provides useful context beyond annotations, though could elaborate on consequences of re-satisfying a gate.

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?

Two sentences, front-loaded with core purpose. Every word earns its place; no redundancy. Efficient and clear.

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, TTL, audit trail, and structured reasoning role. Does not mention output or prerequisites (e.g., gate must exist), but given no output schema and tool simplicity, it is sufficiently complete.

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

Parameters5/5

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

Schema coverage is 100% with parameter descriptions. Description adds meaning: evidence TTL and audit trail behavior for structured reasoning, which is not in the schema. This significantly aids correct usage.

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?

Description clearly states 'Satisfy a gate condition' with verb 'satisfy' and resource 'gate condition'. It distinguishes from sibling gate tools like register_claim_gate (creates gates) and gate_stats (queries gates).

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

Usage Guidelines3/5

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

Implies usage for satisfying a gate condition but provides no explicit guidance on when to use versus alternatives (e.g., register_claim_gate, require_evidence_for_claim). No when-not-to-use or prerequisites mentioned.

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