Skip to main content
Glama
arcnow-io

@arcnow/mcp

Official
by arcnow-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Inspect a platform's fees and defaults

arcnow_platform
Read-onlyIdempotent

Retrieve a platform's configuration: admin, fee split across creator, referrer, platform, and protocol, default migrator, and curve template. Shows basis points as both fee and trade percentages.

Instructions

One platform's configuration: who administers it, who receives its cut, how the 1% trade fee is divided FOUR ways — creator, referrer, the platform and the protocol; there is no developer share — which migrator it launches tokens into by default, and the curve template it stamps onto every token it launches.

With no address, reports arcnow.io's own platform — the default a launch uses.

The single easiest thing to misread here is what a share means. Every share is basis points OF THE FEE, never of the trade. A creator share of 3000 bps is 30% of the fee and 0.30% of the trade. This tool prints both, every time. The platform's own share is never configured: it is the residual, whatever is left after the protocol, creator and referrer shares — arcnow.io's own is creator 3000 / referrer 1000 / platform 3500 / protocol 2500.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressNoOptional: the PlatformConfig address. Defaults to arcnow.io's own platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description adds valuable context beyond them: fee shares are basis points of the fee, not the trade; the platform share is always the residual; and the tool always prints both bps and percentage. This prevents a likely misinterpretation.

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

Conciseness5/5

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

The description is structured in clear paragraphs: what the tool reports, how the optional address behaves, and the critical share-semantics warning. Every sentence carries useful information without redundancy.

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

Completeness5/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 compensates by naming the key returned aspects: administrators, fee recipients, the four-way fee division, migrator default, and curve template. It also clarifies the default no-address case and the exact share semantics, giving an agent enough to understand and invoke the tool correctly.

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 100%, so the baseline is 3. The description reinforces the optionality and default behavior already present in the schema ('Defaults to arcnow.io's own platform') but does not add materially new parameter semantics beyond that.

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

Purpose5/5

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

The description states a specific action and resource: inspecting one platform's configuration, covering administrators, fee splits, migrator defaults, and curve templates. It clearly distinguishes itself from the sibling list tool by saying 'One platform's configuration' rather than a list.

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?

It gives clear usage context, especially the key behavior that omitting the address defaults to arcnow.io's own platform. However, it does not explicitly contrast with arcnow_list_platforms or state when one should be chosen over the other.

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