Skip to main content
Glama
Sign In
yimu-mcp

yimu-mcp

by powercess
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

sync_end

sync_end

End an active sync rate limit session using its sessionId, terminating the sync_start session to release resources and stop rate limiting.

Instructions

结束同步限流会话（免鉴权，POST /bookkeeping/rateLimit/sync/end?sessionId=）。

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

Input Schema

NameRequiredDescriptionDefault
session_idNosync_start 返回的 sessionId

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses that no authentication is required and specifies the HTTP method. It does not describe side effects, error behavior when no session exists, or idempotency, but the action is simple enough that the gap is moderate.

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?

One compact sentence conveys the action, endpoint, HTTP method, and authentication requirement with no filler. Every piece of information earns its place.

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?

For a one-parameter tool this is mostly complete: it gives the endpoint and auth contextmag. But it does not clarify whether session_id is effectively required despite schema marking it optional, and it omits any expectation about response or failure behavior.

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?

The schema already documents session_id as 'sync_start 返回的 sessionId' with 100% coverage publication. The description adds the query-string representation but little semantic value beyond that. Baseline 3 applies.

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 states a specific action ('结束同步限流会话') and resource ('限流会话'), and includes the exact endpoint path. It clearly identifies the tool's function, though it does not explicitly contrast with sibling tools like sync_start or sync_pull.

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 this tool is the counterpart to sync_start by referring to a rate-limit session, and the schema's reference to 'sync_start 返回的 sessionId' reinforces that. However, it never explicitly states when to call it or how it relates to other sync operations.

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