Get started with Unitrader
get_startedHow to start using Unitrader, beginning free with practice money, and the link to sign up.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
get_startedHow to start using Unitrader, beginning free with practice money, and the link to sign up.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety and side-effect profile are covered structurally. The description adds that the payload is a sign-up link and a starting guide with free practice money, but says nothing about the return shape or whether the link requires an account.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with no filler, and the core value (getting-started info plus signup link) is front-loaded. The phrasing 'beginning free with practice money' is slightly awkward but not wasteful.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a parameterless, read-only informational tool with no output schema, the description covers the essentials of what the agent gets back. However, it leaves the boundary with about_unitrader undefined, which is the one gap that could cause a mis-selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters and the schema is empty, so there is nothing for the description to disambiguate. Baseline 4 applies; a brief note that no arguments are ever needed would have made it a 5.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states what the tool returns: onboarding guidance plus the link to sign up, including the free practice-money angle. That is more specific than the name/title alone, though it does not explicitly contrast itself with the sibling about_unitrader, which covers overlapping ground.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use statement, no exclusion of alternatives, and no mention of when an agent should prefer about_unitrader or trading_lesson instead. The newcomer audience is only weakly implied by 'beginning free with practice money'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.