Skip to main content
Glama

Vino & Views

by io.github.oriondrayke
OverviewDiscussionsAdmin

launch_economics

Read-onlyIdempotent

Free. Pons token-specific on-chain pool fee, creator share, initial buy, current deployer holdings and estimated launch-cost break-even volume.

Input Schema

NameRequiredDescriptionDefault
requestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / max_charge_atomic
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Max Charge Atomic"
-}
    • removedInput schema / properties / operation_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Operation Id"
-}
  2. Changed1 schema field changed
    • addedInput schema / properties / operation_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Operation Id"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / max_charge_atomic
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Max Charge Atomic"
+}
  4. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the 'Free' cost note and enumerates the returned metrics (pool fee, creator share, initial buy, deployer holdings, break-even volume), which is useful context beyond annotations but thin given no output schema.

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?

A single compact sentence with the cost qualifier ('Free.') front-loaded. It is efficient, though the dense metric list is harder to parse than a stated verb would be.

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 read-only analytical tool with no output schema, enumerating the produced figures is genuinely helpful. However, the meaning of the version enum and the two numeric inputs is left entirely unexplained, so an agent can infer the return shape but not how to parameterize the call correctly.

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 description coverage is 0% and the request object wraps four fields. The description only loosely implies the 'token' input via 'Pons token-specific' and does not explain the 'version' enum (current/legacy) or what expected_volume_eth and launch_gas_cost_eth should contain. It fails to compensate for the coverage gap.

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 description reads as a noun-phrase list of returned metrics rather than stating a verb+resource action. It does convey that this concerns 'Pons token-specific on-chain' launch economics, but never says outright that it retrieves/computes those figures, and it does not distinguish itself from the sibling launchpad_fee_audit.

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?

'Free.' signals cost, which is the only operational guidance given. There is no statement of when to call this versus launchpad_fee_audit or agent_budget_guard, no prerequisites, and no exclusions.

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

All Vino & Views toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources