Skip to main content
Glama
Sign In

BotsRated (beta)

by com.botsrated
OverviewDiscussionsAdmin

Seller self-check (Free)

seller_self_check
Read-onlyIdempotent

FREE. Read stored measurements for a host you operate or anyone can read: listing versus quoted price, whether recent unpaid checks returned a valid payment request, payTo observations. Not a judgement. Pass probe:true with session (the verified-owner token from POST /v1/seller/claim/verify) to run one on-demand unpaid probe with the same receipt code as buyer checks. probe is rate-limited.

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": {
      "host": "<host>"
    },
    "name": "seller_self_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYesSeller hostname or URL, e.g. blockrun.ai or https://blockrun.ai/api/v1/chat/completions
probeNoVerified owners only. Runs one unpaid probe.
sessionNoOwner session token. Required when probe is true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotent, non-destructive and closed-world, and the description adds real context beyond them: probe requires a verified-owner session token, is rate-limited, and reuses the buyer-check receipt code. It also warns 'Not a judgement', which usefully scopes interpretation of the output. However, it does not clarify that probe causes an outbound request to the seller host (a tension with openWorldHint=false) nor how far back stored measurements reach.

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?

Front-loads 'FREE.' then the core action, with the optional probe path last where it belongs. Sentences are dense but each carries information; the opening clause ('for a host you operate or anyone can read') is slightly garbled and costs a beat of clarity.

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 no output schema, the description compensates by naming the three measurement categories returned, and it covers the auth requirement, the rate limit, and the optional probe mode. It leaves open the recency window of 'stored measurements' and what the probe result actually looks like, minor gaps for a three-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description goes beyond it by giving the provenance of the session token (the verified-owner token from POST /v1/seller/claim/verify) and by tying probe to the buyer-check receipt code and its rate limit. That is genuine added meaning for two of the three parameters.

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 verb and resource: read stored measurements for a host, enumerated as listing vs. quoted price, whether unpaid checks returned a valid payment request, and payTo observations. It is clearly a seller-side measurement read rather than a buyer check, and it references buyer checks as the counterpart, though it never names a sibling tool 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?

Gives an access-scope rule ('a host you operate or anyone can read') and explains how to trigger the on-demand probe, but never says when an agent should call this instead of siblings like check, receipt_verify, or preflight. The default read path versus probe path distinction is implied only by the phrase 'on-demand'.

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

All BotsRated (beta) 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