Anyway Possible Paid Agent Utilities

Start Here: Choose a Tool (Free)

recommend_tool

Read-onlyIdempotent

Use this free tool before paying. Describe the decision you need and receive the best Anyway Possible tool, exact price, required inputs, alternatives, and next step. This tool never triggers payment or calls an external service.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`goal`	Yes	Plain-language description of the decision or evidence the agent needs.
`maxPriceUsd`	No	Optional maximum price in USDC that the recommended paid tool may cost.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`goal`	Yes
`nextStep`	Yes
`maxPriceUsd`	Yes
`alternatives`	Yes
`paymentRequired`	Yes
`recommendedTool`	Yes
`clarifyingQuestion`	Yes
`clarificationNeeded`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 9, 2026

addedInput schema / properties / goal / description

Added value: +"Plain-language description of the decision or evidence the agent needs."

addedInput schema / properties / maxPriceUsd / description

Added value: +"Optional maximum price in USDC that the recommended paid tool may cost."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "alternatives": {
+      "items": {
+        "$ref": "#/properties/recommendedTool/anyOf/0"
+      },
+      "type": "array"
+    },
+    "clarificationNeeded": {
+      "type": "boolean"
+    },
+    "clarifyingQuestion": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "goal": {
+      "type": "string"
+    },
+    "maxPriceUsd": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "nextStep": {
+      "type": "string"
+    },
+    "paymentRequired": {
+      "type": "boolean"
+    },
+    "recommendedTool": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "required": [
+    "paymentRequired",
+    "goal",
+    "maxPriceUsd",
+    "recommendedTool",
+    "alternatives",
+    "clarificationNeeded",
+    "clarifyingQuestion",
+    "nextStep"
+  ],
+  "type": "object"
+}

AddedSep 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds a behavioral guarantee beyond these: 'never triggers payment or calls an external service', which is valuable for an agent deciding whether to invoke it in a constrained environment. It does not contradict annotations and enriches the safety profile.

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 zero fluff. The critical usage instruction ('free tool before paying') is front-loaded, followed by a compact summary of the output and a safety guarantee. Every sentence earns its place; no redundancy.

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-param tool with a provided output schema and annotations covering safety, the description covers what the agent needs: the invocation context (free, non-payment, non-external), the expected output (best tool, price, inputs, alternatives, next step), and the scope of inputs. Nothing material is missing for an agent to call it effectively.

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 description coverage is 100%, so both params (goal and maxPriceUsd) are already documented in the schema. The description's mention of 'Describe the decision you need' aligns with the goal param but adds no new syntax or semantics beyond what the schema provides. Baseline 3 is appropriate when schema carries the descriptive burden.

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?

The description states a specific purpose: to recommend the best tool based on a goal, with a clear verb ('receive') and resource (tool). It distinguishes itself from sibling tools by being a free preliminary step ('Use this free tool before paying'), making it clear it is a meta-tool, not a direct operation like checking balances or URLs.

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

Usage Guidelines4/5

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

Explicitly advises usage 'before paying', indicating this is the first step in tool selection. It also clarifies that it never triggers payment or calls external services, but does not explicitly state when NOT to use it (e.g., if the user already knows the target tool) or name alternative selection mechanisms. Still, the context is clear enough for an agent to route appropriately.

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

All Anyway Possible Paid Agent Utilities tools Inspect

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.