Skip to main content
Glama
openhoat

aik-mcp

by openhoat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

check_updates

Detect outdated installed knowledge items and report newer versions available in the knowledge base, so agents can update rules, skills, or workflows.

Instructions

Check for installed content items that have newer versions available in the knowledge base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentYesTarget AI agent (opencode, claude-code, cline, codex, or copilot).
scopeNoScope to check (project or global).project
projectDirNoProject directory (defaults to current working directory). Config files are found by walking up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.6.0
    • addedInput schema / properties / scope
      Added value: +{
+  "default": "project",
+  "description": "Scope to check (project or global).",
+  "enum": [
+    "project",
+    "global"
+  ],
+  "type": "string"
+}
  2. Changed3 schema fields changedv0.3.1
    • changedInput schema / properties / agent / description
      Previous value: -"Target AI agent. Auto-detected from existing config files if not specified (opencode, claude-code, cline)."New value: +"Target AI agent (opencode, claude-code, cline, codex, or copilot)."
    • changedInput schema / properties / agent / enum
      Previous value: -[
-  "opencode",
-  "claude-code",
-  "cline"
-]New value: +[
+  "opencode",
+  "claude-code",
+  "cline",
+  "codex",
+  "copilot"
+]
    • addedInput schema / required
      Added value: +[
+  "agent"
+]
  3. Addedv0.1.1

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It doesn't say whether this is a read-only operation, whether it contacts a remote knowledge base or needs network/auth, or whether it mutates local state; the word 'check' hints at read-only but nothing is confirmed.

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?

A single front-loaded sentence with no filler. The resource and the condition ('newer versions available') come first, so the agent gets the gist immediately.

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?

With no annotations and no output schema, the description should say more about what a 'check' returns (e.g., a list of outdated items) and whether anything is affected. It is minimally adequate for a simple 3-parameter tool but leaves the result shape and side-effect profile to inference.

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

Parameters3/5

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

Schema description coverage is 100%, with agent and scope carrying enum descriptions and defaults, so the schema already documents all parameters. The description adds no syntax, defaults, or meaning beyond what the schema states, making the baseline 3 appropriate.

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 ('Check') and resource ('installed content items that have newer versions available in the knowledge base'), which clearly separates it from siblings like list_installed and update. It stops short of naming alternatives, but the scope is unambiguous.

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 description implies the use case (checking for outdated items before updating), but never states when to call it versus update, list_installed, or reinstall. No prerequisites or exclusions are given, leaving the agent to infer the workflow.

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

Deploy Server

Other Tools