Skip to main content
Glama
Launch-On-Basis

Basis MCP Server

Official

create_market

Create a prediction market on BNB Smart Chain. Earn 20% of net trading fees from the market you create. Provide a question, outcomes, and end time.

Instructions

Create prediction market. Earn 20% of net trading fees forever. Provide image_url OR image_file_path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
questionYesMarket question
symbolYesMarket token symbol
outcomesYese.g. ['Yes', 'No']
end_timeYesISO date or unix timestamp
seed_usdbNoUSDB seed (min 50, default: 50)
descriptionNo
image_urlNo
image_file_pathNoLocal image file path (alternative to image_url)
Behavior2/5

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

With no annotations provided, the description should disclose behavioral traits. It fails to specify side effects, permission requirements, or whether the operation is idempotent. The only behavioral hint is the fee earning, which is a feature, not a behavioral disclosure.

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 concise with two short sentences, no redundant information. However, it could be better structured to front-load critical usage info. Still, it earns a high score for being succinct.

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 complexity (8 parameters, numerous sibling tools, no output schema), the description is insufficient. It lacks guidance on when to create a market, what the return values are, and how it relates to similar tools like 'pm_create_market'. The AI would need more context to use it correctly.

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

Parameters4/5

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

Schema coverage is high (75%), providing baseline 3. The description adds value by clarifying the mutual exclusivity of 'image_url' and 'image_file_path', which is not evident from the schema. This nuance helps the agent choose correctly.

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 the verb 'Create' and resource 'prediction market', and includes a unique benefit (earning fees). However, it does not differentiate from the sibling tool 'pm_create_market', which likely has similar functionality.

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions a fee incentive but does not indicate prerequisites, restrictions, or contrasting conditions with siblings like 'pm_create_market'.

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