Skip to main content
Glama

axvg_build

Expands a layout spec JSON into complete Axvg JSON with geometry and style encoding. Run it when a verified spec needs conversion into an output Axvg file.

Instructions

把布局规格 JSON 展开为完整 Axvg JSON(几何/样式编码)。 登记证据 channel-a,只适用 capabilities.md 的已验样本。CLI: node axvg.mjs build <spec.json> -o <out.axvg.json>;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_build"
  }
}

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=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds operational detail — that the service injects the subcommand and that only verified samples are valid — but says nothing about failure modes or what happens to existing output files.

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 clauses: purpose first, then the applicability constraint, then the invocation convention. Little waste, though the CLI fragment is dense and could be split for readability.

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 build/transform tool with no output schema and a fully opaque args array, the description covers purpose, constraints, and invocation, which is the core need. It stops short of describing validation behavior or the shape of the produced Axvg JSON.

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?

With a single opaque string-array parameter at 0% schema coverage, the description does useful work by explaining that args omits the subcommand word and follows the CLI form 'build <spec.json> -o <out.axvg.json>'. It still leaves the exact element order and allowed flags only loosely specified.

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 gives a specific verb and transformation: expanding a layout spec JSON into a complete Axvg JSON covering geometry and style encoding. That is concrete enough to distinguish it from sibling tools like axvg_paste or axvg_selftest, though it does not explicitly name an alternative it supersedes.

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 states a precondition that it only applies to samples already verified in capabilities.md, which implies when it is appropriate. However, it never compares against sibling tools or says when not to use it, so the routing guidance is only implied.

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