Skip to main content
Glama

Deps Dev Query

deps_dev_query
Read-onlyIdempotent

Query packages/versions (by hash, repo URL, etc).

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": {
      "query": {
        "hash": "sha256:abc123def456"
      }
    },
    "name": "deps_dev_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesQuery body, see https://docs.deps.dev/api/v3/#query

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"Query body — see https://docs.deps.dev/api/v3/#query"New value: +"Query body, see https://docs.deps.dev/api/v3/#query"
  2. Added

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no rate limits, auth requirements, or explanation of how the open-world lookup behaves when a hash or repo URL is unknown. With annotations present the bar is lower, but this contributes zero extra behavioral context.

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 short sentence with the lookup keys front-loaded and no filler. It is brief rather than padded, though the brevity here reflects under-specification more than discipline.

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?

An output schema exists so return values need not be explained, but this is an open-world endpoint taking a free-form nested query body with several distinct lookup modes. The description plus a docs link is thin for an agent that must construct that body correctly without fetching external documentation.

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%, but the single nested `query` object is documented only by a pointer to the external docs site, leaving its internal shape to the schema examples. The description does add the two concrete lookup modes (hash, repo URL), which is modest value beyond the schema; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Query packages/versions (by hash, repo URL, etc)" gives a verb and a resource plus two example lookup keys, but the verb is generic and the tool is not distinguished from the very specifically named siblings deps_dev_package, deps_dev_version, deps_dev_project and deps_dev_dependencies. An agent cannot tell from the description what this endpoint adds over those.

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?

No when-to-use guidance, no exclusions, and no mention of the sibling package/version/project tools that overlap heavily with this one. The only directional hint is the "etc" after two lookup-key examples, which is inference, not 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.