Skip to main content
Glama
Sign In
british-cybersecurity-mcp

british-cybersecurity-mcp

by Ansvar-Systems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

gb_cyber_get_advisory

Retrieve a specific NCSC security advisory using its reference number. Enter the advisory reference to get details.

Instructions

Get a specific NCSC security advisory by reference (e.g., 'NCSC-ADV-2024-001').

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": {
      "reference": "<reference>"
    },
    "name": "gb_cyber_get_advisory"
  }
}

Input Schema

NameRequiredDescriptionDefault
referenceYesNCSC advisory reference (e.g., 'NCSC-ADV-2024-001')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. While 'Get' implies a read-only operation, the description does not explicitly confirm no side effects, rate limits, or prerequisites. It is adequate but not thorough.

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?

The description is a single, well-structured sentence that front-loads the verb and resource, with an example in parentheses. No unnecessary words.

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 one-parameter get tool, the description is complete enough to convey its purpose and usage. It lacks explicit output description, but the tool name and context imply the returned data. Minor gap prevents a 5.

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% and the description of the 'reference' parameter in the schema includes the same example as the tool description. The description adds no new meaning beyond the schema, so baseline score of 3 is appropriate.

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?

The description clearly states the action ('Get') and the resource ('specific NCSC security advisory'), and includes a concrete example format for the reference. This distinguishes it from sibling gb_cyber_search_advisories, which is for searching/filtering.

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

Usage Guidelines4/5

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

The description implies usage when a specific advisory reference is known, and provides an example. It does not explicitly state when not to use or mention the search alternative, but the sibling tool name and context make it clear.

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