Skip to main content
Glama

sdk-list_deprecations

Lists deprecated Exeris SDK annotations and attributes with replacement guidance, since version, and removal status. Supports filtering by package or for-removal-only items.

Instructions

List all deprecated Exeris SDK annotations and attributes across the authoring contract, including replacement guidance, since version, and forRemoval status. Supports filtering by package or forRemoval only.

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": "sdk-list_deprecations"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageNoOptional package filter (e.g. 'system', 'security', 'capability', or full package name).
forRemovalOnlyNoIf true, only returns items marked for removal (forRemoval: true). Defaults to false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.7/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. It does disclose what each returned record contains (replacement guidance, since version, forRemoval), which is useful, but it says nothing about ordering, volume/pagination, whether the scan is exhaustive across all packages, or cost of the call.

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 sentences, front-loaded with the scope and followed by the filtering capability. No filler, no repetition, and every clause (replacement guidance, since version, forRemoval) tells the agent something actionable about the payload.

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 zero-required-parameter, read-only listing tool with no output schema, the description is nearly sufficient: it enumerates the fields returned so the agent knows what to expect without a schema. The only gap is the absence of ordering or result-size expectations, which matters less for a small contract metadata catalog.

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 description coverage is 100%, both parameters (package, forRemovalOnly) are documented in the schema, and the description restates their effect at a high level along with the default (false). It adds only modest meaning beyond the schema, such as the package examples implied by the scope, so this sits slightly above the baseline.

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: lists deprecated Exeris SDK annotations and attributes across the authoring contract, plus which fields come back (replacement guidance, since version, forRemoval). It is clear this is the deprecation-focused subset rather than the general annotation lister, but it never names the sibling (sdk-list_annotations) it complements, so the differentiation is implied rather than stated.

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 sentence about filtering by package or forRemoval gives some practical guidance on narrowing results, and 'deprecated' frames the context. However, there is no explicit when-to-use versus when-not guidance and no pointer to sdk-list_annotations for the non-deprecated case or sdk-describe_annotation for per-item detail.

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