Skip to main content
Glama

learnjcu_check_update

Read-only

Check GitHub for a newer MCP version and list what it adds; use when users ask about updates or new features.

Instructions

Check whether a newer version of learnjcu-mcp is on GitHub, and list what it adds. Use when the user asks about updates or what is new.

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": "learnjcu_check_update"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-network reach are covered structurally. The description adds the specific external target (GitHub) and the shape of the result (whether a newer version exists plus what it adds), which is useful context beyond the annotations. It does not mention auth, rate limits, or failure behavior when GitHub is unreachable, leaving some gaps against the lower bar set by the 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?

Two short sentences with zero waste: the first states the action and the returned information, the second states the trigger. The purpose is front-loaded ahead of the usage guidance.

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?

With no output schema, the description carries the burden of describing return values, and it does so adequately: existence of a newer version plus a list of what it adds. For a zero-parameter read-only tool this is nearly complete; only the no-update case and error behavior are unaddressed.

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?

The tool takes zero parameters, so there is no parameter meaning to convey and the baseline is 4. The description correctly implies no input is needed by asking the agent only to check and list.

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 and resource: check for a newer version of learnjcu-mcp on GitHub and list what it adds. That is far more specific than the name alone, and the read-only 'check' framing separates it from an install/apply action. It stops short of naming the sibling that actually performs an update, so the differentiation is implied rather than explicit.

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

Usage Guidelines4/5

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

It gives a concrete trigger: 'Use when the user asks about updates or what is new.' That covers the common entry path clearly. It does not state when not to use it or point to a companion tool for applying the update, so it is clear context without exclusions.

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