Skip to main content
Glama

ask_ai

Ask the AI assistant, in natural language, about your real portfolio (analysis, context, risks). It never gives buy or sell orders. Daily limit per account.

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": {
      "question": "<question>"
    },
    "name": "ask_ai"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe question about the portfolio or the market (max. 1000 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden, and it does disclose two real behavioral traits: it will not produce buy/sell recommendations and it is rate-limited daily per account. It omits what the response looks like (free-text answer), what happens when the daily limit is hit, and whether the call has side effects — meaningful gaps for an unannotated tool.

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?

Two compact sentences, front-loaded with the core action and followed by the two guardrails. The 'Daily limit per account' clause is terse to the point of being unquantified, which slightly undercuts its usefulness.

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 one-parameter tool with no output schema, the description covers purpose and two constraints but never indicates the return shape (a natural-language answer) or behavior at the rate limit. Adequate to call correctly, but not complete for predicting what comes back.

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?

Only one parameter, and schema coverage is 100% with a maxLength and description already documenting it. The description adds the notion of phrasing questions in natural language and the topic scope, but nothing about format or length constraints beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource: ask the AI assistant in natural language about the real portfolio, with the subject scope (analysis, context, risks) named. It distinguishes itself from the get_* siblings by being the only conversational/interpretive tool, though it doesn't explicitly say 'use this instead of get_portfolio when you want a synthesized answer'.

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 description implies usage (natural-language questions about portfolio or market) and adds two constraints: no buy/sell orders and a daily per-account limit. However, it never states when to prefer this over get_portfolio / get_metrics or what kinds of questions it handles well versus poorly, leaving routing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources