Skip to main content
Glama

refresh_erispulse_docs

Forces framework documentation cache to match the currently installed framework version, resolving mismatches after framework upgrades.

Instructions

强制同步框架文档缓存到当前已安装框架版本(框架升级后文档对不上时用)。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose the meaningful behavioral trait that this overwrites/force-syncs the cache rather than reading it, and ties it to the installed framework version. It says nothing about cost, duration, whether it can be run concurrently, or failure modes when the version lookup fails — gaps for a mutating cache operation with zero annotation coverage.

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 sentence, front-loaded with the action and object, with the usage condition tucked into a parenthetical. Nothing is redundant or padded.

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 an output schema present and no input parameters, the description does not need to explain return shape. What it covers — action, target, trigger — is sufficient for correct invocation; only side-effect/permission detail is missing, which is minor for a zero-arg cache refresh.

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 nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description adds only the implicit notion of 'current' installed version being resolved server-side, which is useful framing but not required.

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 ('强制同步' / force-sync) and a specific resource (the framework documentation cache), plus the target state (currently installed framework version). This is clearly distinct from the read-oriented siblings like search_erispulse_docs and read_erispulse_doc, though it never names an alternative explicitly.

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 an explicit trigger condition in parentheses: use when documentation does not match after a framework upgrade. That is clear when-to-use guidance; only when-NOT-to-use (e.g., normal lookups, first-time setup) is absent.

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