Skip to main content
Glama

BRAINIAC Cybersecurity Intelligence

Get repository Scorecard

cybersecurity-intelligence_repository-scorecard

Retrieve the official OpenSSF Scorecard result for a GitHub, GitLab or other supported repository. Price $0.05 USDC. POST /api/v1/cybersecurity-intelligence/repository/scorecard. 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": {
      "repository": "<repository>"
    },
    "name": "cybersecurity-intelligence_repository-scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault
repositoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose important operational traits: the call costs $0.05 USDC, uses POST, and fails closed with 402 without executing when unpaid. It does not describe the returned payload shape, rate limits, or caching, but the cost and payment-gating disclosure is materially more than most definitions provide.

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?

Four short sentences, front-loaded with purpose, then cost, endpoint and failure mode. The raw endpoint path is the least useful sentence for an agent but is short and does not bury the important content.

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 one-parameter read tool with no output schema, the definition covers what is fetched, what it costs, and how payment failure behaves. The main remaining gap is the exact repository identifier format, which matters because the schema gives no description for that field.

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 0% and the single parameter 'repository' is only typed as a URI, so the description must compensate. It adds that the repository may be GitHub, GitLab 'or other supported' hosts, which clarifies accepted inputs, but it never states the expected format (full URL vs. owner/repo), leaving the agent to infer from format:uri.

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: 'Retrieve the official OpenSSF Scorecard result' for a repository, which is clearly distinct from sibling tools like dependency-tree, lockfile-audit or vulnerability. It stops short of explicitly naming a sibling to route against, but the resource is unambiguous.

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 or when-not-to-use guidance and no named alternative among the many cybersecurity-intelligence siblings (package-check, risk-assess, dependency-tree). The only conditional information given is a payment prerequisite ('Unpaid calls return 402 and do not run'), which is a precondition rather than usage 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