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

io.github.kushvinth/crowbar

cb_sources

Retrieve provenance for each data source that populated the CVE and exploit index, including upstream URL, license, SHA-256, load time, and row count to verify data origin and integrity.

Instructions

Source provenance: which upstream source filled the index, its URL, license, SHA-256, load time and row count.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.6/5.0
Behavior4/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 does describe the payload an agent will receive: upstream source identity, URL, license, SHA-256, load time and row count. It does not explicitly state that the call is a side-effect-free read or whether results are paginated or cached, which keeps it below 5.

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?

A single compact sentence with the key concept ('Source provenance') front-loaded and the returned fields enumerated after it. The leading noun fragment rather than a full clause is a minor structural weakness, but there is no wasted wording.

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?

With no output schema, no annotations, and no parameters, the description is the only source of information, and it adequately enumerates the returned fields. It could be fuller by stating whether the result covers one source or all sources and whether rows are aggregated, but for a trivial zero-argument lookup it is largely sufficient.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is no argument semantics the description could add. Nothing in the description conflicts with the empty input schema.

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 the resource precisely — source provenance for the index — and enumerates the fields returned (URL, license, SHA-256, load time, row count), so an agent knows exactly what this tool surfaces. It lacks an explicit verb and does not contrast itself with any sibling (cb_tables, cb_stats), so it stops short of a 5.

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 statement, no prerequisite, and no mention of an alternative tool for related metadata such as cb_tables or cb_stats. An agent must infer from the noun phrase alone that this is the provenance lookup, which is thin guidance even for a zero-argument tool.

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