Skip to main content
Glama

axure_state

Read-only

Restores the current Axure session state after context compression by returning a cached snapshot of source files, working-copy chain nodes, timeline, and chain-tail structure in one call.

Instructions

当前会话快照(缓存摘要;重新检查磁盘用 verify):源文件、工作副本链全部节点、timeline、链尾结构三零。上下文被压缩后用一次调用恢复状态。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description's real contribution is disclosing that the data is a cached summary that may be stale, with verify as the disk-truth path. It stops short of describing freshness guarantees or how a snapshot is created/refreshed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the resource front-loaded and the alternative routing in a parenthetical, so no time is wasted. The internal jargon ('链尾结构三零') costs a little readability without adding decodable 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?

With zero parameters and no output schema, the description must carry the burden of what comes back, and it does list the snapshot contents plus the staleness caveat. A rough sense of size or ordering of the returned snapshot would make it fully complete.

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 about argument meaning to add; baseline 4 applies. The description correctly indicates the call is argument-free by framing it as a single one-shot restore.

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?

Names a specific resource (session snapshot) and enumerates its contents: source file, all nodes of the working copy chain, timeline, and chain tail. The parenthetical 'cached summary' distinguishes it from the sibling verify, which reads disk. The phrase '链尾结构三零' is opaque jargon that slightly blurs the purpose, preventing a 5.

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?

Gives an explicit trigger ('after context is compressed, restore state in one call') and routes the agent to the alternative ('to re-check disk, use verify'). That is clear when-to-use and alternative-selection guidance; it lacks an explicit statement of when this tool should not be used at all.

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