UseTested — Receipts-Verified Service Reviews

Get all reviews in a category ($0.05)

get_bundle

Read-onlyIdempotent

Every receipts-verified UseTested review in a category (inference|data|search|media|infrastructure), sorted by reliability. Costs $0.05 via x402 (USDC on Base) — paid automatically by your x402 MCP client.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`category`	Yes	Category of services to fetch reviews for

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`reviews`	Yes
`category`	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": {
+    "category": {
+      "type": "string"
+    },
+    "count": {
+      "type": "number"
+    },
+    "methodology_version": {
+      "type": "string"
+    },
+    "reviews": {
+      "items": {
+        "additionalProperties": {},
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "category",
+    "count",
+    "reviews",
+    "methodology_version"
+  ],
+  "type": "object"
+}

First observedSep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds genuinely new behavioral context: a $0.05 x402/USDC-on-Base payment that is auto-handled by the client, plus receipts-verified filtering and reliability sorting. That is material information an agent would not otherwise know.

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 compact sentences, front-loaded with what is returned, then the payment mechanism. Every clause carries information; no filler.

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, return values need no explanation, and the cost/eligibility details are disclosed. Minor gap is the absence of routing guidance relative to the sibling tools, but the definition is otherwise complete for invocation.

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 and schema coverage is 100%, with the enum values and meaning fully documented in the schema, so the description merely echoes the category list. Baseline 3 applies since the schema carries the parameter burden.

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 resource (receipts-verified UseTested reviews) scoped to a category, with the sort order (by reliability) made explicit. It does not distinguish itself from siblings like get_review, but the resource and scope are clear enough for selection.

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?

Usage is only implied: fetch reviews for a category when you want the full set rather than a single one. No explicit when/when-not guidance or named alternative (get_review, search_services) is provided.

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?