ToolsMonk tool catalog

Run a ToolsMonk tool

run_tool

Read-only

Run a ToolsMonk tool and return its result. Works for business, finance and student calculators, text, developer and document utilities; web tools (seo-checker, site-audit, website-speed-test); regex-tester and regex-generator; AI tools (free-ai-humanizer-tool, ai-image-generator, ai-pdf-summarizer, resume-maker); and light file tools (merge, split, rotate, number or watermark a PDF, resize, convert or compress an image, and more), which take a file the user attached (pass it in the top-level files parameter) or a public https fileUrl (max 10 MB), and return a download link valid for one hour. These have their own small daily limits per account. See list_runnable_tools, or check mcp.runnable from get_tool. Pass the tool slug and an input object matching that tool's input schema. Heavy file tools (OCR, Office conversion, background removal, editors) cannot run here; for those the error message gives the URL to open. Inputs and outputs are not stored.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	Yes	The tool slug, e.g. "roi-calculator-biz" or "json-formatter".
`files`	No	Files the user attached in the conversation, for file tools. Fills the tool's `fileUrl` (first file) or `fileUrls` (all files) when `input` does not give one. Max 10 MB each.
`input`	No	Arguments for the tool, as described by its input schema.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 15, 2026

changedInput schema / properties / slug / description

Previous value: -"The tool slug, e.g. \"bmi-calculator\" or \"json-formatter\"."New value: +"The tool slug, e.g. \"roi-calculator-biz\" or \"json-formatter\"."

Changed1 schema field changedSep 26, 2026

addedInput schema / properties / files

Added value: +{
+  "description": "Files the user attached in the conversation, for file tools. Fills the tool's `fileUrl` (first file) or `fileUrls` (all files) when `input` does not give one. Max 10 MB each.",
+  "items": {
+    "properties": {
+      "download_url": {
+        "description": "Temporary link to the attached file.",
+        "type": "string"
+      },
+      "file_id": {
+        "description": "The assistant's id for the file.",
+        "type": "string"
+      },
+      "file_name": {
+        "type": "string"
+      },
+      "mime_type": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "download_url",
+      "file_id"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

AddedSep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint/destructiveHint/openWorldHint/idempotentHint, but the description adds substantive behavior: per-account daily limits, 10 MB file cap, a download link valid for one hour, inputs and outputs are not stored, and the graceful-failure path for unsupported heavy tools. This is exactly the context annotations cannot carry.

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?

Front-loaded with the core action, then the routing detail, then limits and constraints — a sensible order. The middle catalogue of tool categories is long and list-heavy, but each item earns its place by helping the agent decide whether this dispatcher can serve the request.

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?

With no output schema, the description still explains the return shape (download link valid one hour), the error behavior for unsupported tools, the file-size limit, daily limits, and the no-storage guarantee. For a dispatcher with nested objects and a required slug, nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining the cross-parameter interaction the schema cannot express: attached files in top-level `files` fill the tool's `fileUrl` (first file) or `fileUrls` (all files) when `input` doesn't provide one, plus the 10 MB limit. The `input` object is correctly described as matching the target tool's own schema.

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?

States a specific verb and resource ("Run a ToolsMonk tool and return its result") and then concretely enumerates the tool categories it dispatches to. It draws a hard boundary against the heavy file tools it cannot run, so an agent can tell this apart from siblings like list_runnable_tools or get_tool without opening a 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?

Names the alternatives explicitly ("See list_runnable_tools, or check `mcp.runnable` from get_tool") and states the when-not case: heavy file tools (OCR, Office conversion, background removal, editors) cannot run here and the error message supplies the URL instead. It also states the precondition that file tools need an attached file or a public https fileUrl.

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

All ToolsMonk tool catalog tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?