Skip to main content
Glama
Sign In
OnlineCyberTools MCP (280+ filterable tools)

OnlineCyberTools MCP (280+ filterable tools)

by Jambozx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

search

Find relevant online cybersecurity tools by searching the catalogue with keywords or tokens. Returns up to 25 ranked results with details.

Instructions

Keyword search across the Online Cyber Tools catalogue. Returns up to 25 ranked matches with their URL, API URL, description, and category.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch query — substring or whitespace-separated tokens.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Discloses up to 25 ranked matches but does not mention case sensitivity, error handling, or any rate limits. Adequate but could be more detailed.

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 purpose and key details. No fluff; every sentence adds value.

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?

Given the simplicity (1 parameter, no output schema), the description fully explains what the tool returns and its constraint (25 results). No gaps.

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 parameter description already matching the tool description's semantics. The tool description does not add additional meaning beyond what is in the schema.

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?

Clearly states keyword search across the Online Cyber Tools catalogue. Specifies return fields (URL, API URL, description, category) and limit of 25 ranked matches. Distinct from siblings which are mostly specific conversion/encoding tools.

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?

Implies use for general search but does not explicitly compare with alternatives or provide when-to-use/not-to-use guidance. No exclusions or alternative tool names mentioned.

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

Deploy Server

Other Tools