Skip to main content
Glama

ToolsMonk tool catalog

by com.toolsmonk
OverviewDiscussionsAdmin

Run a ToolsMonk tool

run_tool
Read-only

Run a ToolsMonk tool and return its result. Works for calculators, health formulas, text, developer and document utilities; web tools (seo-checker, site-audit, website-speed-test, currency-converter); 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
NameRequiredDescriptionDefault
slugYesThe tool slug, e.g. "bmi-calculator" or "json-formatter".
filesNoFiles 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.
inputNoArguments for the tool, as described by its input schema.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false), and the description adds substantial operational behavior beyond them: file tools return a download link valid for one hour, file tools have small daily limits, inputs and outputs are not stored, and heavy-tool failures are handled by returning a URL. No contradiction with annotations.

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?

The core purpose is front-loaded in the first sentence, and every subsequent sentence carries distinct value (scope specifics, file mechanics, limits, fallback, privacy). The second sentence is a very long run-on that mixes scope enumeration with file-handling mechanics, making it heavier to parse than necessary — docking one point.

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 complex dispatcher tool with no output schema, the description is remarkably complete: invocation pattern, supported categories with concrete examples, both file-passing mechanisms with size limits, result format for file tools, quota behavior, exclusions, fallback, and data-retention policy. There is no output schema, so the description carries the burden — and it meets it.

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?

Schema coverage is 100% and the schema descriptions are already detailed — the files param even documents the fileUrl/fileUrls mapping and the 10 MB limit. The description adds the alternative of passing a public https fileUrl in input and reinforces the slug+input pattern, but this is marginal on top of a fully-documented schema, so the baseline of 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?

Opens with a specific verb and resource — 'Run a ToolsMonk tool and return its result' — and immediately distinguishes itself from the sibling discovery tools (list_tools, search_tools, get_tool) which only browse metadata. It further scopes itself by enumerating exactly which tool categories it can execute and explicitly naming ones it cannot.

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 explicit invocation guidance ('Pass the tool slug and an input object'), points to alternatives for discovery ('See list_runnable_tools, or check mcp.runnable from get_tool'), and states clear exclusions with a fallback ('Heavy file tools cannot run here; for those the error message gives the URL to open'). Also flags daily per-account limits for file tools.

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 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