Skip to main content
Glama
jigyasudham

veto

by jigyasudham
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

veto_dep_advisor

Read-only

Reads package.json or requirements.txt, checks exact dependency versions against OSV.dev, and returns a risk-ranked upgrade plan with breaking-change flags.

Instructions

Reads package.json (using the installed or package-lock version of each dependency) or requirements.txt, queries OSV.dev (free, no key) for known vulnerabilities in those exact versions, and returns a risk-ranked upgrade plan with breaking-change flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ecosystemNoPackage ecosystem: 'npm', 'pypi', 'cargo', or 'auto' (default).
project_dirYesAbsolute path to the project directory.
agent_responseNoPhase 2 response from the host AI (JSON). Pass this back when prompted by the server to complete the agentic loop.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.9.0
    • addedInput schema / properties / agent_response
      Added value: +{
+  "description": "Phase 2 response from the host AI (JSON). Pass this back when prompted by the server to complete the agentic loop.",
+  "type": "object"
+}
  2. First observedv2.7.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so safety and network scope are covered. The description adds meaningful context beyond that: OSV.dev is free and needs no key, and it pins to the installed/package-lock version rather than the declared range, which changes what gets scanned. Return shape is also characterized (risk-ranked plan with breaking-change flags).

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?

A single dense sentence that front-loads the input, the external call, and the output. Nothing is wasted and no padding is present.

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, the description usefully characterizes the return value. It does not explain the multi-phase agentic loop implied by agent_response, but that dangling interaction is documented in the schema, so the gap is minor.

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 100%, so the schema already documents all three parameters including the ecosystem enum. The description adds only marginal input meaning, implying that auto-detection covers both npm and pypi manifests, so baseline 3 is appropriate.

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?

States a specific verb chain (reads manifests, queries OSV.dev, returns a risk-ranked upgrade plan) with the exact resource (package.json/requirements.txt). It's clear what the tool does, but it never distinguishes itself from the obvious sibling veto_dep_verify, leaving the agent to guess which to call.

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 alternatives are named. With siblings like veto_dep_verify and veto_security_scan present, the omission of routing guidance is a real gap.

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