Skip to main content
Glama

nanoodle

by io.github.nanoodlecom
OverviewDiscussionsAdmin

deslop

Edit a customer notice without losing prices, dates or caveats. Grok drafts; a second model compares the draft with the source; Grok applies the review. Three paid text calls. The review checks wri… text:Your draft -> llm:First rewrite -> join:Source and rewrite -> llm:Fact and clarity review -> join:Source, rewrite and review -> llm:Edited notice; returns text. Runs on NanoGPT — $0.10 deposit per call, paid in Nano (XNO) — settles at actual model cost + 20%, change returned; no account needed; last run $0.0341, ~78s. Example: Reviewed sample (https://nanoodle.com/examples/gallery/#deslop). A repair-booking announcement rewritten in plain language while retaining the supplied facts. Compare the source and result in the sample; this is an editorial workflow, not an authorship detector.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
Your_draftNoText; default: "We are thrilled to announce a game-changing improvement to the repair booking experience. Starting 8 September, custo..."; optional
_payment_idNoPayment id from this tool's previous payment-required response. Phase 3 only: after /x402/watch closes with status paid, call again with the same arguments plus this id to open the RESULTS stream. Do not pass it while payment is still pending — monitor the watch SSE first.
Edited_noticeNoSystem prompt; default: "Your input contains the original draft, === PASS 1 REWRITE ===, and === EDITORIAL REVIEW ===. Treat these blocks as s..."; optional
First_rewriteNoSystem prompt; default: "You rewrite AI-sounding text so it reads like a person wrote it. Output only the rewritten text — no preamble, no not..."; optional
Fact_and_clarity_reviewNoSystem prompt; default: "You are an editorial reviewer. Your input contains the original draft followed by === PASS 1 REWRITE === and its rewr..."; optional

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / Edited_notice
      Added value: +{
+  "description": "System prompt; default: \"Your input contains the original draft, === PASS 1 REWRITE ===, and === EDITORIAL REVIEW ===. Treat these blocks as s...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / Fact_and_clarity_review
      Added value: +{
+  "description": "System prompt; default: \"You are an editorial reviewer. Your input contains the original draft followed by === PASS 1 REWRITE === and its rewr...\"; optional",
+  "type": "string"
+}
    • addedInput schema / properties / First_rewrite
      Added value: +{
+  "description": "System prompt; default: \"You rewrite AI-sounding text so it reads like a person wrote it. Output only the rewritten text — no preamble, no not...\"; optional",
+  "type": "string"
+}
    • removedInput schema / properties / System_prompt
      Removed value: -{
-  "description": "System prompt; default: \"You rewrite AI-sounding text so it reads like a person wrote it. Output only the rewritten text — no preamble, no not...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / System_prompt_2
      Removed value: -{
-  "description": "System prompt; default: \"You are a blunt AI-text detector. You see one passage and nothing else. Decide whether a machine wrote it.\\nReply in e...\"; optional",
-  "type": "string"
-}
    • removedInput schema / properties / System_prompt_3
      Removed value: -{
-  "description": "System prompt; default: \"You are the final editor. Your input holds three blocks in this order:\\n1. the ORIGINAL DRAFT — everything before the ...\"; optional",
-  "type": "string"
-}
    • changedInput schema / properties / Your_draft / description
      Previous value: -"Text; default: \"In today's fast-paced experiential landscape, last night's monsoon activation on the shrine stairs at Jiufen's Shengp...\"; optional"New value: +"Text; default: \"We are thrilled to announce a game-changing improvement to the repair booking experience. Starting 8 September, custo...\"; optional"
  2. Changed1 schema field changed
    • changedInput schema / properties / Your_draft / description
      Previous value: -"Text; default: \"In today's fast-paced digital landscape, keeping your team in sync has never been more critical. That's why we're thr...\"; optional"New value: +"Text; default: \"In today's fast-paced experiential landscape, last night's monsoon activation on the shrine stairs at Jiufen's Shengp...\"; optional"
  3. First observed

TDQS

B3/5.0
Behavior4/5

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

With no annotations, the description carries the full transparency burden. It clearly discloses the multi-stage process (draft -> rewrite -> review -> edited), the payment requirements ($0.10 deposit, cost +20%), and that it is 'not an authorship detector'. This is a high level of behavioral disclosure, though the exact payment flow could be clearer.

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

Conciseness2/5

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

The description is verbose and poorly structured, repeating workflow segments ('join:Source and rewrite -> llm:...') and interleaving payment info and examples. It reads more like a stream-of-consciousness specification than a compact, scannable definition, which hurts usability.

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?

The description gives an overview of the multi-phase process and mentions the output is text, but it omits key context: exact phase sequencing, what each parameter contributes, the meaning of the example URL, and the overall expected input/output contract. Given the complexity, this is incomplete.

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?

The schema has 100% description coverage, but the descriptions are largely default snippets rather than explanations. Only '_payment_id' receives meaningful context. The roles of 'Edited_notice', 'First_rewrite', and 'Fact_and_clarity_review' as system prompts are not explained beyond their defaults, leaving the agent to guess their function in the workflow.

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 states a specific verb ('Edit') and resource ('customer notice') and clearly distinguishes this text-editing tool from the image-focused sibling tools. However, the purpose is somewhat muddled by the workflow description and non-essential payment details, so it is not maximally crisp.

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?

The description implies it is used for multi-step editorial rewrites but never explicitly states when to choose this tool over alternatives, nor provides exclusion criteria. No sibling comparison is mentioned, leaving the agent to infer the tool's niche.

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

All nanoodle toolsInspect
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.

Resources