UseTested — Receipts-Verified Service Reviews

Get receipts-verified service review (free)

get_review

Read-onlyIdempotent

Full receipts-verified review of one agent-economy service: BUY/CAUTION/AVOID verdict, scores, measured latency/error rate, and on-chain purchase receipts. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`service`	Yes	Exact service name, as listed by search_services (free)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`scores`	Yes
`service`	Yes
`verdict`	Yes
`endpoint`	Yes
`measured`	Yes
`receipts`	Yes
`updated_at`	Yes
`price_per_call`	Yes
`refund_behavior`	Yes
`methodology_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "endpoint": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "measured": {
+      "additionalProperties": false,
+      "properties": {
+        "calls_tested": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "error_rate": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "latency_p50_ms": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "latency_p95_ms": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "latency_p50_ms",
+        "latency_p95_ms",
+        "error_rate",
+        "calls_tested"
+      ],
+      "type": "object"
+    },
+    "methodology_version": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price_per_call": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "receipts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "amount": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "chain": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "payer": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "ts": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "tx": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "chain",
+          "tx",
+          "ts",
+          "payer",
+          "amount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "refund_behavior": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "scores": {
+      "additionalProperties": false,
+      "properties": {
+        "docs": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "quality": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "reliability": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "value": {
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "reliability",
+        "quality",
+        "value",
+        "docs"
+      ],
+      "type": "object"
+    },
+    "service": {
+      "type": "string"
+    },
+    "updated_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verdict": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "service",
+    "endpoint",
+    "verdict",
+    "scores",
+    "measured",
+    "price_per_call",
+    "receipts",
+    "refund_behavior",
+    "note",
+    "methodology_version",
+    "updated_at"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the lower bar applies. The description usefully adds what the review actually contains — verdict tiers, scores, measured latency/error rate, on-chain purchase receipts — which tells the agent what evidence backs the result.

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?

A single front-loaded sentence that packs the scope and the return contents with no filler. Minor redundancy between "receipts-verified" and "on-chain purchase receipts," and "Free" duplicates the title, but it stays tight.

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

Completeness4/5

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

With an output schema present and rich annotations covering the safety profile, the description need not explain return formatting. Combined with the schema's parameter documentation, the definition is complete enough to invoke correctly; only sibling routing and prerequisites are absent.

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?

Only one parameter exists and the schema documents it at 100% coverage, including the exact-name requirement and the search_services reference. The description adds nothing beyond restating the single target as "one agent-economy service," so the baseline 3 applies.

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?

States a specific verb and resource (get a review of one agent-economy service) and enumerates the payload: BUY/CAUTION/AVOID verdict, scores, latency/error rate, on-chain receipts. The choice of "one" service implicitly separates it from get_bundle, but neither sibling is named, so differentiation is left to inference.

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

Usage Guidelines3/5

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

There is no explicit when-to-use or when-not-to-use guidance, nor any routing to get_bundle or search_services. The repeated "Free" label and the schema's pointer to "as listed by search_services" hint at a lookup-after-search workflow, but the description itself only implies the context.

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

All UseTested — Receipts-Verified Service Reviews 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.

Resources

Need Help?