Skip to main content
Glama
CyberSafe MCP

CyberSafe MCP

by kshitij9896

get_daily_cyber_tip

Retrieve a short, jargon-free daily cybersecurity tip for phone, laptop, AI, or general safety. Use it to build practical security habits with one clear action each day.

Instructions

Get one short, jargon-free daily cybersecurity tip.

Args: category: One of 'phone', 'laptop', 'ai', or 'general'.

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": "get_daily_cyber_tip"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNogeneral

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description must carry behavioral disclosure, and it does characterize the output as a single short, jargon-free tip (a safe, trivial read). It omits whether the tip is stable per-day or randomized, and whether invalid categories error or silently fall back to a default.

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?

One front-loaded sentence states purpose and output shape, followed by a compact Args block with only the one parameter. No filler, nothing that could be cut without losing information.

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?

An output schema exists, so return values need not be described, and the sole optional parameter's value set is documented. What remains thin is category semantics — how each category changes the tip — but for a one-parameter, zero-required tool this is close to sufficient.

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?

Schema description coverage is 0% and no enums are declared, yet the description supplies the exact valid values ('phone', 'laptop', 'ai', 'general'), which is genuine added meaning beyond the schema. It does not restate the 'general' default, which the schema already carries.

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?

"Get one short, jargon-free daily cybersecurity tip" pairs a concrete verb with a concrete resource and adds output qualities (short, jargon-free, one item). It is clearly distinguishable in kind from the sibling diagnostic/check tools, though it never names them explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The word "daily" faintly implies a once-a-day cadence, but nothing tells the agent whether to call this instead of, or alongside, check_password_hygiene, analyze_scam_message, or the other siblings.

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