Skip to main content
Glama

racket_check_lite

Read-onlyIdempotent

FREE lite Racket Check of a local service provider's website URL. Runs the same scan as racket_check but returns the verdict (CLEAN / PLAN_PUSH / RACKET / UNKNOWN) and the 0-100 score only — no evidence snippets, no signal detail. Use this to triage whether a provider deserves the full racket_check report, or call racket_check directly for the complete evidence-backed scan.

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": {
      "url": "<url>"
    },
    "name": "racket_check_lite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesService provider website URL to check for racket signals, e.g. https://example-lawncare.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely new context: it is free, it runs the same scan as racket_check, and it deliberately omits evidence snippets and signal detail, which tells the agent what it will not get back. It stops short of stating auth, rate-limit or cost-cap details beyond 'FREE'.

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, front-loaded with the lite/free framing and the returned fields, then the routing advice. No filler, no restating of the tool name alone, and the contrast with the sibling is packed efficiently into the closing clause.

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?

There is no output schema, so the description carries the return-value burden and does so precisely: verdict tokens, 0-100 score, and the explicit absence of evidence snippets and signal detail. For a one-parameter read-only scan, nothing an agent needs to select or invoke it is missing.

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 coverage is 100% with a single required url parameter whose example is already in the schema, so the description is not obliged to expand on it. The description names the verdict enum values, but that is output semantics rather than parameter meaning, so the baseline of 3 applies.

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?

States a specific verb and resource ('lite Racket Check of a local service provider's website URL') and immediately pins down the output shape (verdict CLEAN / PLAN_PUSH / RACKET / UNKNOWN plus 0-100 score), which cleanly separates it from the sibling racket_check with its full evidence report.

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

Usage Guidelines5/5

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

Gives an explicit decision rule: use this to triage whether a provider deserves the full racket_check report, or call racket_check directly for the complete evidence-backed scan. Both the when-to-use and the alternative are named, with no inference required.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.