toolradar

verify_price

Read the vendor's pricing page now and check the stored prices against it. Returns each plan's result, the read date and a hash of the page. Needs a free API key; one read per tool per day.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "verify_price"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`context`	No	Optional. In a few words, what the user is trying to do. No names, emails or other personal data.

Output Schema

Name	Required	Description
`url`	No
`plans`	No
`readAt`	No
`confirmed`	No	Every stored paid price is printed on the page
`pageSha256`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 30, 2026

addedInput schema / properties / context

Added value: +{
+  "description": "Optional. In a few words, what the user is trying to do. No names, emails or other personal data.",
+  "type": "string"
+}

AddedOct 30, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the free API key requirement and a per-tool daily read limit, plus what the response contains (per-plan results, read date, page hash). It omits whether the stored prices are modified as a result, which matters given readOnlyHint=false.

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?

Three short sentences, action front-loaded, no filler. The auth/rate-limit note and return summary each carry information an agent needs.

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

Completeness3/5

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

Return values are covered by the output schema and the auth/rate-limit constraints are stated, but for a tool whose annotations flag it as non-read-only and non-idempotent, the description should clarify whether stored prices are updated and whether repeated calls compound costs.

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?

With only 50% schema description coverage, the description must compensate; 'the vendor's pricing page' weakly implies slug identifies the vendor, but it never explains the slug format or what the optional context field is for. It adds minimal field-level meaning.

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 concrete action: read the vendor's pricing page and check stored prices against it. That is specific enough to separate it from siblings like get_pricing (stored data only), though it never names an alternative explicitly.

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?

The phrase 'read ... now' implies a fresh-live-check scenario, and the once-per-day limit hints at when it is appropriate, but there is no explicit statement of when to prefer get_pricing or other siblings over this tool.

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

All toolradar 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.