Skip to main content
Glama
AKzar1el

nofax

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Request human refinement

nofax_request_refinement

Request free-text refinement from a human via iOS Shortcut. Returns a durable requestId for polling until completion.

Instructions

Ask the human for free-text refinement through the configured Nofax Refine iOS Shortcut. Use this when free-text edits are needed; use nofax_request_approval for Allow/Deny or nofax_request_choice for predefined options. Returns a durable pending requestId; call nofax_wait_for_response and repeat while pending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoOptional refinement prompt title shown to the human; defaults to "Nofax refinement".
messageYesContext or draft the human should refine with free text.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusYesThe request is unresolved and must not be treated as approval.
mustWaitYesSignals that the caller must keep waiting for a terminal human response.
requestIdYesDurable Nofax request handle.
instructionYesFail-closed next-step instruction for the caller.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.7
    • addedInput schema / properties / message / description
      Added value: +"Context or draft the human should refine with free text."
    • addedInput schema / properties / title / description
      Added value: +"Optional refinement prompt title shown to the human; defaults to \"Nofax refinement\"."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "instruction": {
+      "description": "Fail-closed next-step instruction for the caller.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "mustWait": {
+      "const": true,
+      "description": "Signals that the caller must keep waiting for a terminal human response.",
+      "type": "boolean"
+    },
+    "requestId": {
+      "description": "Durable Nofax request handle.",
+      "maxLength": 84,
+      "minLength": 24,
+      "type": "string"
+    },
+    "status": {
+      "const": "pending",
+      "description": "The request is unresolved and must not be treated as approval.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "requestId",
+    "mustWait",
+    "instruction"
+  ],
+  "type": "object"
+}
  2. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations indicate mutation (readOnlyHint false) but description adds the asynchronous nature (durable pending requestId, polling via wait_for_response) and external shortcut prerequisite. It doesn't cover cancellation or timeout, but the key behaviors are disclosed.

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 with the primary action front-loaded and no filler; every sentence earns its place by adding purpose, usage, or follow-up guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 2-parameter tool with an output schema, the description covers purpose, usage, alternatives, and the pending/waiting workflow. Nothing essential is missing.

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?

Input schema covers both parameters fully (100% coverage) with clear descriptions, so the description adds little beyond reinforcing that 'message' is the free-text context. Baseline 3 applies.

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 states a specific verb ('Ask') and resource ('the human for free-text refinement') and explicitly names sibling tools with their use cases, making it easy to distinguish from nofax_request_approval and nofax_request_choice.

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?

Provides explicit when-to-use ('when free-text edits are needed') and when-not-to-use alternatives (Allow/Deny vs predefined options), plus follow-up instruction to call nofax_wait_for_response and repeat while pending.

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