Skip to main content
Glama
io.github.kushvinth/crowbar

io.github.kushvinth/crowbar

cb_os

Query Windows MSRC and Apple OS security advisories by platform, impact, date, or exploited status to find relevant vulnerabilities.

Instructions

Vendor OS advisories: Windows (MSRC Security Update Guide) and Apple iOS/iPadOS/macOS security releases. Filter by platform, impact (RCE, EoP, DoS, InfoDisclosure, Spoofing, Bypass) or exploited.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
sinceNo
impactNo
platformNo
exploitedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it only names the upstream data sources. It says nothing about read-only semantics, default result size beyond the schema default, sort order, pagination behavior, or what a result entry looks like.

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 the resource and source scope, then the filter surface. No filler and no repetition of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no annotations and no output schema, the definition is too thin: it omits the meaning of query/since/limit, the time-window semantics, and any sense of the returned advisory shape or ordering. An agent can construct a basic call but cannot confidently predict or bound the response.

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 0% across six parameters, so the description must compensate, and it partially does: it enumerates the impact values (RCE, EoP, DoS, InfoDisclosure, Spoofing, Bypass) that the schema leaves as an unconstrained string, and it maps platform to Windows/Apple families. However, query, since, and limit receive no explanation at all, leaving half the parameters undocumented.

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 names a specific resource (vendor OS advisories) and scopes it precisely to two sources: Windows MSRC Security Update Guide and Apple iOS/iPadOS/macOS security releases. That distinguishes it from generic siblings like cb_advisory or cb_cve, though it never explicitly states the contrast.

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?

It hints at usage by listing the available filters (platform, impact, exploited), so an agent can infer how to narrow results. But there is no explicit when-to-use guidance and no routing to or exclusion of alternatives such as cb_advisory or cb_kev for exploited-in-the-wild queries.

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