Skip to main content
Glama

explain_binding

Read-only

Explains RP/1 text or progress-bar binding expressions, including dependencies, initial values, compiled refresh events, and display precision so you can verify static compilation behavior without runtime observation.

Instructions

解释 RP/1 文字或进度条绑定的完整表达式、依赖、初始值、实际编译出的刷新事件和显示精度。静态编译关系,不冒充原生运行观测。重名用 page/id 或源码指针。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "explain_binding"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYesRP/1 源码 .rp1/.json 路径或 JSON 对象。
targetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish a read-only, closed-world, non-destructive profile, and the description adds a meaningful caveat that the result reflects static compile relationships rather than native runtime behavior. It also lists what will be exposed, which tells the agent what to expect in the response. Nothing about failure modes (e.g., binding not found) is stated.

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?

Three short, front-loaded sentences: purpose first, then the static-vs-runtime caveat, then disambiguation advice. The enumeration of output facets is dense but earns its place by telling the agent what comes back.

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 no output schema, the description usefully lists the returned facets (expression, dependencies, initial value, refresh events, precision) and flags the static-analysis limitation. For a two-parameter read-only tool this is close to sufficient; error/empty-result behavior is the only notable omission.

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 documents only 'source' (path or JSON object); 'target' is undocumented. The description partially compensates by noting that ambiguous names can be resolved with page/id or a source pointer, which hints at how target is addressed. It still does not define target's accepted syntax, so the 50% coverage gap is only partly filled.

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 definition names a specific verb/resource pair ('explain' an RP/1 text or progress-bar binding) and enumerates the output facets: expression, dependencies, initial value, compiled refresh events, display precision. It does not say how this differs from inspection-oriented siblings such as inspect or locate, so it stops short of 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?

'静态编译关系,不冒充原生运行观测' clearly marks the boundary: use this for static analysis, not runtime observation. It also gives disambiguation advice for duplicate names (page/id or source pointer). No alternative tool is named as an explicit substitute, keeping it below 5.

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