AlphaYou: Smart Money Intel

Check AlphaYou research limits

get_alphayou_capabilities

Read-only

Use for requests to start copy trading or subscribe to alerts. Returns that this connector supports research only. It does not connect wallets, fund, sign, place orders, start copying, or create alerts or scheduled tasks.

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": {
      "request": "<request>"
    },
    "name": "get_alphayou_capabilities"
  }
}

Input Schema

Name	Required	Description	Default
`address`	No	Public wallet address, 0x plus 40 characters
`request`	Yes	Which feature the user asked about

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 12, 2026
- addedInput schema / properties / address / description
```
Added value: +"Public wallet address, 0x plus 40 characters"
```
- addedInput schema / properties / request / description
```
Added value: +"Which feature the user asked about"
```
First observedOct 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is given. The description adds genuinely new behavioral information: this tool performs no wallet connection, funding, signing, ordering, copying, or scheduling, and its output is a refusal/limits statement rather than an action. It does not describe the exact response shape, but the substance is well beyond the annotations.

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?

Three short sentences, front-loaded with the trigger and then the limit. The negation list is deliberately enumerated but slightly redundant with the opening sentence's phrasing about copying and alerts, which is the only real waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description correctly carries the burden of saying what comes back ('supports research only'). For a two-parameter, single-enum guardrail tool it is nearly complete; the only gap is the unexplained optional address parameter.

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 description coverage is 100%, with both the address pattern and the request enum documented in-schema, so the baseline is 3. The description adds no meaning about the parameters, and notably never explains why an optional wallet address matters for a capabilities check that explicitly does not connect wallets.

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 states concretely that the tool's return is a research-only capability notice ('Returns that this connector supports research only'), which is a real verb+resource statement rather than a restatement of the name. It also implicitly separates this guardrail tool from the many research/activity siblings, though it does not name any sibling explicitly.

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

Usage Guidelines4/5

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

The trigger condition is explicit and front-loaded: 'Use for requests to start copy trading or subscribe to alerts.' The exclusion clause ('does not connect wallets, fund, sign, place orders...') covers the when-not side well. What is missing is routing to the actual research siblings for legitimate research queries, so it stops short of full alternative-naming.

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

All AlphaYou: Smart Money Intel 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?