Skip to main content
Glama

Version history of one symbol

symbol_history
Read-onlyIdempotent

Trace a public Python symbol's version history—first and last release, signature changes, deprecations, removals, and replacements—before coding against an API from training data.

Instructions

Version history of one public symbol, e.g. package='httpx', path='httpx.Client.init': first and last release it exists in, signature changes, deprecations, removals, and replacement candidates. Use before writing code against an API you remember from training data. A path no indexed release has is not an error: it returns ever_seen=false. For many symbols at one installed version, use check_symbols.

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": {
      "package": "<package>",
      "path": "<path>"
    },
    "name": "symbol_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesPublic dotted path; the package prefix may be omitted.
packageYesPyPI distribution name, e.g. 'langchain-core'.

Output Schema

NameRequiredDescriptionDefault
noteNo
pathYes
eventsNo
indexedYesFalse when the package is not in DepTime's coverage; see the `coverage` tool.
packageYes
internalNoTrue when the name isn't public API: a private name, a name a module imports for its own use, or a name in a private module. Code that uses one, usually another library, breaks when it changes, with no deprecation first.
ever_seenNoFalse means no indexed version ever exposed this public path.
last_seenNo
first_seenNo
suppressedNoEvents left out by the project's suppressions; `note` says so whenever it isn't 0.
replacementsNo
present_in_latestNo
latest_indexed_versionNo
signature_at_last_seenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.13
    • changedOutput schema / $defs / HistoryEvent / properties / kind / description
      Previous value: -"added | removed | deprecated | param_added | param_removed | param_kind_changed | kind_changed | moved | param_deprecated | param_now_required (a default was removed) | param_now_optional (a default was added)"New value: +"added | removed | deprecated | param_added | param_removed | param_kind_changed | kind_changed | moved | param_deprecated | param_now_required (a default was removed) | param_now_optional (a default was added) | now_raises (the callable's body now does nothing but raise `detail.message`)"
  2. Changed1 schema field changedv0.1.10
    • addedOutput schema / $defs / HistoryEvent / properties / affects
      Added value: +{
      +  "description": "diff_versions with used_symbols: the used paths below this one that this change takes with it. A removed, moved or retyped module or class takes its members (they read missing from `version` on); an `added` one means they didn't exist before `version`.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "title": "Affects",
      +  "type": "array"
      +}
  3. Changed1 schema field changedv0.1.8
    • addedOutput schema / properties / suppressed
      Added value: +{
      +  "default": 0,
      +  "description": "Events left out by the project's suppressions; `note` says so whenever it isn't 0.",
      +  "title": "Suppressed",
      +  "type": "integer"
      +}
  4. Changed2 schema fields changedv0.1.5
    • changedOutput schema / $defs / Replacement / properties / source / description
      Previous value: -"deprecation_message: the library's deprecation text; moved_heuristic: a removal paired with an addition in the same release; curated: reviewed by hand; error_message: named by the error text you passed, and found in the index."New value: +"deprecation_message: the library's deprecation text; moved_heuristic: a removal paired with an addition in the same release, or with another path that still has the same object; curated: reviewed by hand; error_message: named by the error text you passed, and found in the index."
    • addedOutput schema / properties / internal
      Added value: +{
      +  "default": false,
      +  "description": "True when the name isn't public API: a private name, a name a module imports for its own use, or a name in a private module. Code that uses one, usually another library, breaks when it changes, with no deprecation first.",
      +  "title": "Internal",
      +  "type": "boolean"
      +}
  5. Changed2 schema fields changedv0.1.4
    • addedOutput schema / $defs / Replacement / properties / source / description
      Added value: +"deprecation_message: the library's deprecation text; moved_heuristic: a removal paired with an addition in the same release; curated: reviewed by hand; error_message: named by the error text you passed, and found in the index."
    • changedOutput schema / $defs / Replacement / properties / source / enum
      Previous value: -[
      -  "deprecation_message",
      -  "moved_heuristic",
      -  "curated"
      -]New value: +[
      +  "deprecation_message",
      +  "moved_heuristic",
      +  "curated",
      +  "error_message"
      +]
  6. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and closed-world, so safety is covered; the description adds the non-obvious behavior that a missing path returns ever_seen=false rather than raising, which meaningfully shapes how an agent handles the response. It also sketches the shape of the report (first/last release, deprecations, replacement candidates) beyond what the hints state.

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?

Four sentences, each doing distinct work: scope, purpose, usage trigger, missing-path semantics, and sibling routing. The identity and scope come first, the caveat and alternative follow, with no filler or repetition of name/title.

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?

The tool is a two-required-parameter read with a full output schema, so return values need not be explained; combined with annotations the description covers identity, usage, error semantics, and the sibling boundary. Nothing an agent needs in order to invoke it correctly is missing.

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 100%, so both parameters are documented structurally; the description still adds value by modelling the paired call shape (package plus a dotted path such as 'httpx.Client.__init__'), which clarifies that the path is a nested public member rather than a module or file. It does not add format or length constraints, which the schema already carries.

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?

States a specific verb+resource: version history of one public symbol, enumerated as first/last release, signature changes, deprecations, removals, and replacement candidates. The concrete example (package='httpx', path='httpx.Client.__init__') makes the unit of analysis unambiguous and lets an agent distinguish it from check_symbols, which is named as the batch alternative.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use before writing code against an API you remember from training data') and an explicit exclusion with the alternative to use instead ('For many symbols at one installed version, use check_symbols'). It also pre-empts the failure-mode question by saying an unindexed path is not an error.

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