Skip to main content
Glama

list_versions

Lists indexed versions of a project, including commit, date, and size, so you can select the version to search.

Instructions

List indexed versions of a project with commit, date and size.

Args:
    project: project id from list_projects (e.g. 'kserve', 'llm-d').

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "list_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. The verb 'List' and the qualifier 'indexed' usefully signal a read-only operation scoped to indexed (not all) versions, but it says nothing about ordering, pagination, or whether all versions are returned. An output schema exists, so the return fields need not be re-explained.

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?

Two short lines, front-loaded with purpose, with the parameter note as supporting detail. The 'Args:' block is slightly redundant with the schema but the example values earn their space.

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?

For a one-parameter list tool with an output schema and a referenced upstream tool, most of what an agent needs is present. Gaps remain around result size/pagination behavior and ordering, which matter for a listing tool with no annotations to fall back on.

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?

Schema coverage is 0% for the single parameter, so the description must compensate, and it does: it identifies 'project' as an id obtained from list_projects and supplies concrete example values ('kserve', 'llm-d'). What remains unclear is the accepted format beyond free-form examples.

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 and resource ('List indexed versions of a project') and names the fields surfaced (commit, date, size), which is more than a restatement of the name. It does not explicitly contrast with siblings, but none of the listed siblings (list_projects, get_page_outline, read_chunks, search_docs, whats_new) overlap in scope.

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?

The 'project id from list_projects' note gives an implied prerequisite workflow, so an agent knows to call list_projects first. There is no explicit when-not guidance, no mention of alternatives, and no statement about what happens for projects with no indexed versions.

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