Skip to main content
Glama

Check skill updates

check_skill_updates
Read-onlyIdempotent

Compare installed skill versions with active versions in the vault.

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": {
      "installed": "<installed>"
    },
    "name": "check_skill_updates"
  }
}

Input Schema

NameRequiredDescriptionDefault
installedYes

Output Schema

NameRequiredDescriptionDefault
dataYes
viewYes
workspaceNo
generated_atYes
schema_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description adds only one piece of extra context, that comparison is against the 'active versions in the vault' — it says nothing about how missing or uninstalled skills are handled or how differences are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundancy. It is efficient, but its brevity for a tool with entirely undocumented parameters borders on under-specification rather than tightness.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the input side is wholly unexplained despite 0% schema description coverage and a non-trivial nested structure. For a comparison tool, the agent also lacks any statement of how results are keyed or what 'active version' means operationally.

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

Parameters2/5

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

Schema description coverage is 0% for a single nested-array parameter requiring skill_slug and installed_version (plus an optional 64-char content_hash, min/max item bounds). The description only alludes to 'installed skill versions' and never explains the array-of-objects shape, the role of content_hash, or the 100-item cap, so it does not compensate for the schema gap.

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?

The description names a specific verb ('Compare') and both resources involved: installed skill versions and active versions in the vault. An agent can tell this is a version-drift check rather than a fetch or write, though it never explicitly contrasts itself with siblings like get_skill or list_my_skills.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance, no prerequisites (e.g. must the skill already be installed?), and no named alternative for related needs such as retrieving a single skill's details. The agent must infer the use case purely from the name and the word 'Compare'.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources