Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Get package project health

cybersecurity-intelligence_package-project-health

Return project activity indicators, repository associations, package metadata and available security information using Google deps.dev API. Price $0.05 USDC. POST /api/v1/cybersecurity-intelligence/package/project-health. Unpaid calls return 402 and do not run.

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": {
      "ecosystem": "<ecosystem>",
      "packageName": "<packageName>"
    },
    "name": "cybersecurity-intelligence_package-project-health"
  }
}

Input Schema

NameRequiredDescriptionDefault
ecosystemYes
packageNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the payment model ($0.05 USDC), the failure mode for unpaid calls (402, call does not execute), and the HTTP endpoint; however, it says nothing about missing-package behavior, rate limits, or whether results are cached/live, which matters for a read tool whose safety profile is undeclared.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, followed by cost and endpoint details, with no filler. The endpoint path is arguably redundant with the tool identity, but overall it is dense and readable.

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

Completeness3/5

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

The description enumerates the categories of returned data, which partly compensates for the absence of an output schema, and it covers the payment gate. It is still incomplete given zero annotation coverage and undescribed parameters — error semantics and input formatting are unaddressed for a tool that requires two inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description needs to explain the parameters and does not mention either one. The ecosystem enumeration is self-evident from the schema's enum list, but 'packageName' gets no format guidance (case sensitivity, scoped names, registry-specific naming), leaving real ambiguity for a required input.

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 verb and resource ('Return project activity indicators, repository associations, package metadata and available security information') and identifies its data source (Google deps.dev API). An agent can tell it is a broad informational lookup rather than a scan, but the phrase 'available security information' is vague enough that the boundary with package-check and vulnerability is not crisp.

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 statement of when to use this tool instead of the sibling tools such as package-check, package-batch-check, vulnerability, or risk-assess. The only conditional text concerns payment (unpaid calls return 402), which is a billing constraint rather than usage guidance, so the agent must infer selection criteria.

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