Skip to main content
Glama
Sign In
tongji-ai-usage

tongji-ai-usage

by KimBrine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

检查积分面板更新

tongji_check_update
Read-onlyIdempotent

Checks the plugin's GitHub repository for an official release and notifies you when an update is available, without downloading or running software.

Instructions

检查本插件 GitHub 仓库的正式版本，仅提示更新，不下载或执行软件。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine value beyond them by stating that it only reports and never downloads or executes software, which sets a hard boundary on side effects. It does not discuss network failure behavior or how the notice is surfaced, keeping it short of a 5.

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 zero filler: it states what is checked, where, and what the tool will not do. Nothing could be removed without losing meaning.

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 parameterless, read-only check with no output schema and full annotation coverage, the description supplies enough to call it correctly and understand its limits. The only mild gap is that the shape of the returned notice is not described, though '仅提示更新' implies a message.

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 the baseline is 4. The description correctly implies no input is needed to perform the check.

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 the official version in the plugin's GitHub repository - and makes clear it is an update check rather than a general version query. It is distinguishable from siblings like get_tongji_usage or tongji_login, though it does not explicitly name them.

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 usage context is implied: call this when you want to know whether a newer official release exists. The phrase '仅提示更新' (only notifies of updates) hints at scope, but there is no explicit when-to-use vs. when-not guidance or reference to alternatives.

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