Skip to main content
Glama

What DepTime indexes

coverage
Read-onlyIdempotent

Lists indexed packages and version ranges to check whether DepTime can answer questions about a dependency before querying changes or replacements.

Instructions

Lists indexed packages and version ranges. If a package is missing, DepTime cannot answer about it. Takes no arguments; call it first when unsure whether a package is covered.

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": "coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
policyYes
packagesYes
index_built_atYes
configured_but_not_indexedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.8
    • addedOutput schema / $defs / CoverageEntry / properties / latest_released_at
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "When latest_version was uploaded to PyPI. A release newer than the index is answered for latest_version, the nearest one it has.",
      +  "title": "Latest Released At"
      +}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds useful behavioral context: coverage determines whether DepTime can answer at all, and the tool takes no arguments. It does not describe response shape, but an output schema exists.

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?

The description is three short sentences and front-loads what the tool lists. Every sentence adds useful information about scope, limitations, and usage. There is no redundant or filler text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-argument coverage-listing tool with annotations and an output schema, the description supplies everything an agent needs. It explains what is indexed, the consequence of missing coverage, and when to call it.

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 has zero parameters, so the baseline is 4. The description reinforces that it "takes no arguments," which is consistent with the empty schema but adds no further parameter semantics.

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

Purpose5/5

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

The description states a specific verb and resource: "Lists indexed packages and version ranges." It also clarifies the semantic boundary that missing packages cannot be answered about. This clearly distinguishes the coverage-checking tool from symbol-focused siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

It gives explicit usage guidance: "call it first when unsure whether a package is covered." That is a clear trigger for using this tool before other lookups. It does not name sibling alternatives or state when not to use it, so it falls short of a full 5.

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