Skip to main content
Glama

Deps Dev Project

deps_dev_project
Read-onlyIdempotent

Fetch deps.dev project metadata for a GitHub, GitLab, or Bitbucket repository (e.g. project_key="facebook/react"), returning scorecard scores, version count, and linked package references.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_key": "facebook/react",
      "project_type": "github"
    },
    "name": "deps_dev_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_keyYesPlain "owner/repo", e.g. "facebook/react", do not URL-encode it.
project_typeYesgithub | gitlab | bitbucket

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_key / description
      Previous value: -"Plain \"owner/repo\", e.g. \"facebook/react\" — do not URL-encode it."New value: +"Plain \"owner/repo\", e.g. \"facebook/react\", do not URL-encode it."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description usefully names the payload (scorecard scores, version count, linked package references) and the external deps.dev source, but that overlaps an existing output schema, and nothing is said about missing repos, rate limits, or auth.

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 front-loaded sentence with the resource first, the supported hosts parenthetically, and the return shape last — no filler. The trailing return-value list is mildly redundant given the output schema, which keeps it from a 5.

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 two-parameter read-only lookup with full schema coverage, rich annotations, and an output schema, the description supplies enough to call it correctly. Only edge-case behavior (unknown repo, cross-host key format) is left unaddressed, which is minor at this complexity.

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 schema already documents both fields plus examples, so the description's 'e.g. project_key="facebook/react"' and host enumeration largely restate structured data. It confirms accepted hosts but adds no syntax or format detail beyond the 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?

States a specific verb (Fetch) and resource (deps.dev project metadata) scoped to a repository across GitHub/GitLab/Bitbucket, with a concrete project_key example. It implicitly separates itself from deps_dev_package/version/dependencies by being project-level, but never names a sibling explicitly, 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 Guidelines3/5

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

Usage is only implied: an agent can infer 'use this for repo-level scorecard data rather than package-level lookups', but there is no explicit when-to-use, when-not-to-use, or named alternative. The reader must supply the routing logic themselves.

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.