Skip to main content
Glama
Sign In

Pentest requests, security headers checker, guides

by com.penetrationtestservices
OverviewDiscussionsAdmin

Search penetrationtestservices.com

search_site
Read-onlyIdempotent

Search the guides, service pages and research on penetrationtestservices.com. Returns titles, URLs and one-line summaries.

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": {
      "query": "<query>"
    },
    "name": "search_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1 to 20)
queryYesWords to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results to return (1 to 20)"
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds genuinely useful behavior beyond that: it names the indexed corpus and, importantly given there is no output schema, states the return shape as titles, URLs and one-line summaries.

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 short sentences with zero waste, leading with what is searched and following with what comes back. Nothing is repeated from the schema or annotations.

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 simple two-parameter read-only search, the definition covers scope and return shape, which matters because no output schema exists. Minor gaps remain around result ordering, empty-result behavior, and whether summaries are truncated, but nothing blocks correct invocation.

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 description coverage is 100%, with both query and limit documented including the 1–20 range and default of 8, so the baseline is 3. The description adds no search syntax, operator, or matching-behavior detail beyond what the schema provides.

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 specific verb and resource ('Search the guides, service pages and research on penetrationtestservices.com'), making the corpus scope unambiguous. It does not explicitly contrast with siblings such as get_page, which retrieves a page once found, so it falls just short of 5.

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?

Usage is implied by 'search' — an agent can infer this is the discovery step before fetching content. However, there is no explicit when-to-use, when-not-to-use, or named alternative such as get_page for full-page retrieval.

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

All Pentest requests, security headers checker, guides 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