Skip to main content
Glama

List Rever services and prices

list_services
Read-only

Free. Lists all Rever website-intelligence tools with their price, so you can pick the cheapest one for the job.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_services"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered without the description. The description adds two genuinely new behavioral facts: calling it is free, and the response carries per-tool prices. It does not say anything about the shape of the returned list, which matters somewhat more because there is no output schema.

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?

A single sentence, front-loaded with the cost fact ('Free.') that an agent needs to decide whether to call it. Every clause carries information: catalog contents, price inclusion, and the selection rationale.

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?

For a no-argument, no-output-schema listing tool this covers what it returns (tools plus their prices) and why it exists. The only real omission is any hint about the return structure, such as names, ordering, or whether prices appear as fields, which an agent may need before chaining into a purchase decision.

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?

The tool takes no parameters, so the baseline of 4 applies. There is nothing to document and the description does not waste space inventing parameter details.

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 ('Lists all Rever website-intelligence tools') and adds the distinguishing payload, each tool's price. That clearly separates it from the analysis siblings (seo_audit, headers, dns, etc.), which each return findings rather than a catalog.

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

Usage Guidelines4/5

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

Gives a clear reason to call it: 'so you can pick the cheapest one for the job', which implies it should be used before selecting a paid analysis tool. There is no explicit when-not guidance, but for a zero-argument catalog tool the triggering condition is unambiguous.

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.