Skip to main content
Glama

Tseha

by io.tseha

Get component updates

get_component_updates
Read-only

Returns per-component breaking changes and a migration guide between an installed version of the project's active component package and the latest published version. Read-only: it reports an upgrade, it never performs one. Use it when planning or reviewing a component-library upgrade, or before bumping the package version in a manifest. current_version is the exact semver currently installed, e.g. "1.0.0" - not a range, so no leading "v", "^", or "~"; read it from list_packages when unsure. Passing the latest version returns an empty change set. It is not a per-component changelog and not a current spec - use get_component for one component today, and list_packages for what is installed. Requires update tracking, a Team plan feature; on lower plans it returns an upgrade-required error instead of data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idYesUUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns "Project not found or access denied" rather than empty data, and a project withheld by a plan limit returns a plan error that retrying cannot clear. Changes are computed against this project's active package, so current_version must be the version of that package and not of some other dependency.
current_versionYesThe version currently installed, e.g. "1.0.0"

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Project ID from list_projects"New value: +"UUID as returned by list_projects - not the project name, title, or slug, and not guessable. Fetch it once and reuse the same id across tools. An id outside the caller's organization returns \"Project not found or access denied\" rather than empty data, and a project withheld by a plan limit returns a plan error that retrying cannot clear. Changes are computed against this project's active package, so current_version must be the version of that package and not of some other dependency."
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

The readOnlyHint annotation is reinforced with 'Read-only: it reports an upgrade, it never performs one,' and the description goes further by disclosing edge-case behavior (passing the latest version returns an empty change set) and the plan-dependent error. It also surfaces error behavior for an invalid project_id instead of silently returning data. No contradictions with annotations.

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?

Seven sentences, each carrying non-redundant information: core result, read-only nature, use cases, version syntax, empty-set behavior, distinct-from alternatives, and plan requirement. The core purpose is front-loaded in the first sentence, and no filler or repeated schema content exists.

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 read-only 2-parameter tool with no output schema, this is as complete as needed: it explains the result shape, exact parameter syntax, source of truth for parameters, error conditions, and feature requirements. An agent can call this tool correctly on its first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds critical semantic detail to both parameters: current_version must be an exact semver without 'v', '^', or '~', and project_id is a UUID from list_projects that cannot be guessed. It also clarifies the connection between the two parameters ('Changes are computed against this project's active package, so current_version must be the version of that package'), which the schema alone does not establish.

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 opens with a precise verb-resource pair: 'Returns per-component breaking changes and a migration guide between an installed version ... and the latest published version.' It clearly differentiates this from siblings by naming what it is not ('not a per-component changelog and not a current spec') and pointing to get_component and list_packages as the alternatives.

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?

Usage context is explicit: 'Use it when planning or reviewing a component-library upgrade, or before bumping the package version in a manifest.' It also defines exclusions and alternative tools, and states a hard prerequisite (update tracking Team plan) with the failure mode on lower plans. An agent can decide to use this tool vs others without ambiguity.

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

All Tseha toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.8/5.0
Disambiguation5/5

Each tool has a clearly distinct resource and role: enumeration (list_*), lookup (get_*), search, updates, and metadata. Even the closely related list_components and search_components are sharply separated by exact-name enumeration versus ranked by-use-case search.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, using either list_* for enumerations or get_* for single-item or metadata lookups. Naming choices clearly signal the operation type and resource without exceptions.

Tool Count5/5

With 9 tools, the server is well-scoped for read-only access to a project's design system, component catalog, standards, and style tokens. Each tool has a distinct responsibility and none feel redundant or superfluous.

Completeness5/5

The surface fully covers the read-only domain: project discovery, package listing, component enumeration and search, component details, version updates, standards, and style tokens. It leaves no obvious dead ends for an agent needing design system information.

Resources