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

tongji-ai-usage

by KimBrine
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

刷新同济 AI 用量

get_tongji_usage
Read-onlyIdempotent

Retrieve Tongji University AI credit balances and usage for today, yesterday, or the last 7 days, with an optional force refresh to request updated data.

Instructions

读取同济 AI 积分和用量；force 请求刷新，后端仍有短暂防重复缓存。

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

Input Schema

NameRequiredDescriptionDefault
forceNo
rangeNotoday

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so safety is covered. The description adds genuinely non-obvious behavior: even with force, the backend keeps a short anti-duplicate cache, so a refresh may not reflect an immediate re-query. It stops short of describing auth requirements or response contents.

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 compact sentence, front-loaded with the core action and followed by the one nuance that matters. No filler or repetition of schema fields.

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?

There is no output schema, yet the description says nothing about what the returned credits/usage data looks like or its shape. Combined with undocumented 'range' semantics, an agent must guess at both the time-window behavior and the result format.

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 0%, so the description carries the burden. It does explain the semantics of 'force' (request a refresh, subject to a backend duplicate-suppression cache), which meaningfully extends the bare boolean. However, the 'range' parameter (today/yesterday/7d) is never mentioned, so the enum is left to speak for itself.

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 and resource: reads Tongji AI credits and usage (读取同济 AI 积分和用量). That is distinguishable from open_tongji_panel, tongji_check_update and tongji_login without opening the schema, though the description never explicitly contrasts itself with those siblings.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. The only conditional language ('force 请求刷新') is parameter behavior rather than routing guidance between this tool and its siblings.

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