Skip to main content
Glama

Ni Biashara Shelves — Africa FX, freight & compliance checks (x402)

Defensive security insights — physical/RF self-audit

get_cyber_insights
Read-only

Defensive security insights — physical/RF self-audit. The Ni Biashara cybersecurity shelf's defensive insights set: what consumer RF/NFC/BLE/USB tools demonstrate, what it means for a small business, how to check your OWN exposure, and how to harden. Defensive awareness only — no offensive content. $0.05 USDC on Base. Returns the x402 URL to GET (402 → PAYMENT-SIGNATURE → delivery). Free to call this tool; payment happens on the URL.

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

Input Schema

NameRequiredDescriptionDefault
insight_categoryNoinsight category on the record, e.g. Wi-Fi, NFC / RFID access control (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already establish readOnly, non-destructive and open-world, and the description adds real behavior beyond them: the $0.05 USDC-on-Base price, the x402 handshake (402 → PAYMENT-SIGNATURE → delivery), and the key distinction that calling this tool is free while payment occurs against the returned URL. That resolves the biggest agent-facing ambiguity for a paid tool. It stops short of saying what the delivered payload looks like (format, length, delivery mechanism) once payment clears.

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?

Front-loaded with purpose, then scope, then a safety boundary, then price and payment mechanics, in roughly priority order. Each sentence carries a distinct fact and none are padding; the only minor redundancy is restating the title's phrase, which is one clause.

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 zero-required-param, no-output-schema tool, the essentials are covered: what content the shelf contains, that it is defensive-only, and how the paid delivery works. What is missing is the shape of the delivered artifact and whether omitting insight_category returns a bundle or a single record — meaningful for an agent deciding whether to pass the filter.

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 a single optional param, so the schema already carries the semantics and the 3 baseline applies. The description does not mention insight_category at all — not what values are meaningful, nor that omitting it returns the whole set. No value beyond the schema is added.

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 resource and scope: a defensive-insights set covering what consumer RF/NFC/BLE/USB tools demonstrate, business implications, self-exposure checks, and hardening. That is far more than a restatement of the name. However, it never distinguishes itself from adjacent cyber siblings such as get_cyber_exposure_dossier or get_cyber_daily_brief, and the 'self-exposure' phrasing actively overlaps with the dossier, so an agent cannot route between them from the text alone.

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 only implied: the defensive framing plus the enumerate/understand/check/harden content list suggests when the tool is relevant. There are no explicit when-to-use or when-not-to-use statements, and no named alternative for the exposure-check use case it partially claims. 'Defensive awareness only — no offensive content' is a useful boundary but is a content constraint, not selection guidance.

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.

Resources