keyfo

Schedule buy

schedule_buy

Plan a weekly buy of a stock token on Robinhood Chain for wallet: usd or eth each week on weekday at hour in tz. Nothing is bought or signed now. The plan starts only after the wallet’s owner confirms it at https://keyfo.xyz/app, signed in with that wallet. At each time keyfo prepares a fresh trade and a sign link; the owner signs it in their own wallet within 6 hours, or that buy is marked missed and the plan goes on. Limits: 5 plans per wallet, $500 per buy, $1000 a week per wallet.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "token": "<token>",
      "wallet": "<wallet>",
      "weekday": "<weekday>",
      "hour": "<hour>"
    },
    "name": "schedule_buy"
  }
}

Input Schema

Name	Required	Description	Default
`tz`	No	IANA time zone, like Europe/Kyiv or America/New_York. UTC by default.	UTC
`eth`	No	ETH to spend on each buy. Give usd or eth, not both.
`usd`	No	Dollars of ETH to spend on each buy, at the ETH price at that time. Up to 500.
`hour`	Yes	Hour of the day in tz, from 0 to 23.
`token`	Yes	Ticker, like NVDA, or the token address.
`wallet`	Yes	The wallet that buys and signs. Its owner confirms the plan at https://keyfo.xyz/app.
`weekday`	Yes	Day of the week: monday to sunday.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing that nothing is signed immediately, that the plan is inert until owner confirmation at keyfo.xyz/app, that each cycle produces a fresh trade and 6-hour sign link, and what happens on a miss. It also quantifies hard limits: 5 plans per wallet, $500 per buy, $1000/week.

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?

Front-loaded with the action, then prerequisites, then the per-cycle mechanics, then limits. Every sentence carries distinct operational information with no filler.

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?

For a scheduling tool with no output schema, it covers what an agent needs: no immediate transaction, out-of-band owner confirmation, signing window, miss handling, and quotas. Nothing material is missing for correct invocation.

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 100%, so the schema already documents each field; the description still adds useful framing by tying usd/eth to a per-buy basis and reinforcing 'usd or eth' exclusivity. The $500/$1000 limits add a constraint not expressed in the schema.

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 first sentence gives a specific verb and resource: 'Plan a weekly buy of a stock token on Robinhood Chain for wallet', with cadence parameters spelled out. 'Nothing is bought or signed now' effectively separates it from immediate-execution siblings like buy_at_price, though no sibling is named explicitly.

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?

The recurring-weekly framing implies when to use it, and the owner-confirmation prerequisite is clearly stated. However, it never explicitly says to prefer this over buy_at_price for one-off purchases, nor does it name cancel_schedule/list_schedules for managing existing plans.

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

All keyfo tools Inspect

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

Need Help?