Skip to main content
Glama

axvg_selftest

Read-only

Validates built-in geometry and encoding assertions as a no-file self-check and records channel-a evidence for verified capabilities.md samples.

Instructions

内置几何/编码断言自检,不产出文件。 登记证据 channel-a,只适用 capabilities.md 的已验样本。CLI: node axvg.mjs selftest;args 省略子命令词,服务自动加入。

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": {
      "args": "<args>"
    },
    "name": "axvg_selftest"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.5

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false; the description reinforces this by stating no files are produced. It adds the side effect of registering evidence to 'channel-a', which is useful, but does not describe the pass/fail output or how failures are surfaced.

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 sentences, each carrying distinct information (what it does, precondition, argument convention) with no filler. Density is high but the ordering is logical and front-loaded.

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, no-output-schema tool, the description covers the invocation convention and precondition but omits what the self-test returns or how results should be interpreted. The missing return-value guidance is the main gap for a diagnostic tool.

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% for the single `args` array, so the description must carry the burden. It does add one critical piece of meaning — that the subcommand word is omitted because the service inserts it — but gives no indication of what other arguments are accepted or their format.

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 concrete operation: a built-in self-test of geometry/encoding assertions that produces no files. It is distinguishable from the sibling build/paste/edit tools, but the phrases 'channel-a' and 'capabilities.md' are undefined jargon that leave the exact scope partly opaque.

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?

It gives a real precondition: only applicable to already-verified samples in capabilities.md. However, it never says when to run the self-test versus other diagnostics (e.g., diagnose_prototype, inspect) or what to do when the precondition is not met.

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