Skip to main content
Glama
Launch-On-Basis

Basis MCP Server

Official

create_gradual_vesting

Create a gradual vesting schedule for tokens, specifying beneficiary, amount, start time, and duration to release tokens over time.

Instructions

Create gradual vesting schedule.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
beneficiaryYesRecipient wallet
tokenYesToken address
amountYes
start_timeYesUnix timestamp
duration_daysYes
time_unitNo0=Second, 1=Minute, 2=Hour, 3=Day
memoNo
ecosystemNoEcosystem token address (default: MAINTOKEN)
Behavior1/5

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

No annotations are present, and the description fails to disclose any behavioral traits beyond the bare action. It does not mention permissions, side effects, or what constitutes a gradual vesting schedule. The minimal text adds no transparency.

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?

The description is a single concise sentence with no extraneous words. However, its brevity sacrifices useful content, though it is well-structured for a minimal description.

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?

Given the tool has 8 parameters, 5 required, and no output schema, the description is severely incomplete. It does not explain the vesting schedule concept, parameter roles, or return value, leaving the agent with insufficient context to use the tool 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?

The description does not explain any parameters beyond what the input schema already provides. With 63% schema coverage, the description should compensate for missing parameter descriptions but does not, leaving parameters like 'amount' and 'duration_days' unexplained.

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 clearly states it creates a gradual vesting schedule, but does not differentiate from sibling tools like batch_create_gradual_vesting or create_cliff_vesting, leaving ambiguity about when to use this specific tool.

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 guidance is provided on when to use this tool over alternatives. Sibling tools exist for batch creation and cliff vesting, but the description offers no context or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Launch-On-Basis/MCP-TS'

If you have feedback or need assistance with the MCP directory API, please join our Discord server