Skip to main content
Glama

ArcHive

arc_product_scaffold

Skeleton of a third-party product: container + enclave kit, app-compose, manifest, propose() parameters, then timelock and activate (bpsOperator + bpsAuthor + bpsNetwork = 10,000).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
railNo
imageNo
priceNoprice per unit in USDC
minBondNo
modelIdNo
bpsAuthorNo
bpsNetworkNo
bpsOperatorNo
descriptionNo
exposureCapNo
deterministicNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It hints at a multi-step propose/timelock/activate flow and one validation rule (bps sum = 10,000), but omits permissions, side effects, reversibility, on-chain vs file-generation behavior, and failure modes.

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

Conciseness3/5

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

It is short and front-loads 'Skeleton of a third-party product,' but the colon-and-plus-sign list is cryptic and reads as a fragment rather than a structured explanation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, multi-stage scaffolding tool with no annotations or output schema, the description is far too thin. It gives only a high-level artifact list and one parameter constraint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 8% across 12 parameters. The description clarifies the three bps fields and their sum constraint, but leaves name, rail, image, minBond, modelId, exposureCap, deterministic, and others undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The fragment identifies the resource ('Skeleton of a third-party product') and lists artifacts/components, but never states the action as a verb and does not distinguish it from siblings such as arc_operator_plan or arc_bounty_prepare_create. An agent can guess it scaffolds a product, but the purpose is not cleanly stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no named alternatives. The only workflow hint is 'then timelock and activate,' which describes sequence rather than selection criteria.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.