Skip to main content
Glama

waiaas_pm_setup

Configure Polymarket API keys and optionally approve CTF contracts for a specified wallet to enable prediction market operations.

Instructions

Set up Polymarket API keys and optional CTF contract approval for a wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
wallet_idYesWallet ID (required).
auto_approveNoAutomatically approve CTF contracts.

Implementation Reference

  • The tool 'waiaas_pm_setup' is registered and implemented in this handler. It takes a wallet_id and auto_approve flag, sending a POST request to the Polymarket setup endpoint.
    server.tool(
      'waiaas_pm_setup',
      withWalletPrefix('Set up Polymarket API keys and optional CTF contract approval for a wallet.', walletContext?.walletName),
      {
        wallet_id: z.string().describe('Wallet ID (required).'),
        auto_approve: z.boolean().optional().describe('Automatically approve CTF contracts.'),
      },
      async (args) => {
        const walletId = args.wallet_id;
        const body: Record<string, unknown> = {};
        if (args.auto_approve !== undefined) body.auto_approve = args.auto_approve;
        const result = await apiClient.post(`/v1/wallets/${walletId}/polymarket/setup`, body);
        return toToolResult(result);
      },
    );
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions 'CTF contract approval' hinting at on-chain activity, but omits critical mutation details: whether this requires gas/transaction signing, if idempotent, or side effects like token allowances being set.

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?

Single efficient sentence with action verb front-loaded. Zero waste. Every clause earns its place by describing the two distinct operations (API keys setup + optional approval).

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 2-parameter setup tool with no output schema, the description covers the basics but lacks behavioral context expected for a configuration tool involving API credentials and contract approvals (e.g., permanence, security implications).

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 has 100% coverage with 'Wallet ID (required)' and 'Automatically approve CTF contracts'. Description reinforces auto_approve is 'optional' (maps to non-required param) but adds no syntax, format, or domain context beyond schema descriptions.

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?

Clear verb+resource combo ('Set up Polymarket API keys') and distinguishes from sibling waiaas_pm_get_* tools which are read-only data fetchers. Slightly vague on what 'set up' entails (generation vs. configuration).

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

Usage Guidelines3/5

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

Implied usage as initialization step given 'setup' in name and description, plus contrast with sibling read operations. However, lacks explicit 'use this before other Polymarket operations' or prerequisite guidance.

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/minhoyoo-iotrust/WAIaaS'

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