PentestCompare: pentest provider data

List penetration testing providers

list_providers

Read-onlyIdempotent

List providers from the PentestCompare dataset with optional filters. Facts come from each provider's own pages with check dates. Unknown values are 'Not published'.

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_providers"
  }
}

Input Schema

Name	Required	Description
`scope`	No	Every listed scope must be 'yes'
`delivery`	No
`published_prices_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare this as a safe, idempotent, closed-world read, so the bar is lower. The description adds genuinely non-obvious behavior: facts are sourced from each provider's own pages and carry check dates, and missing data is rendered as 'Not published' rather than omitted — that sentinel matters for interpreting results.

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?

Three short sentences with the core purpose front-loaded and no wasted words. The middle sentence ("Facts come from each provider's own pages with check dates") is slightly compressed but still parses.

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?

For a zero-required-param list tool with no output schema, the description covers provenance and the 'Not published' placeholder, which is the most important interpretation aid. It still leaves the semantics of two of the three filters and any indication of result size/shape unaddressed.

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

Parameters2/5

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

Schema description coverage is only 33% (only `scope` is documented, and its AND-semantics only appear in the schema). The description adds no meaning for `delivery` (human-led/hybrid/automated) or `published_prices_only`, so half the filter surface is left unexplained in both places.

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?

The description states a specific verb and resource ("List providers") and names the dataset (PentestCompare), so the agent knows exactly what comes back. It does not explicitly contrast with the sibling get_provider (single-record lookup) or search_site, but the plural listing intent is clear.

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?

"with optional filters" implies the tool can be used either as a full enumeration or a filtered query, and the scope parameter's 'every listed scope must be yes' clarifies AND-semantics. No explicit when-to-use versus when-not-to-use guidance, and no mention of the sibling get_provider for detail lookups.

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

All PentestCompare: pentest provider data 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?