Skip to main content
Glama

Search the Optionscanner Learn library

learn_search
Read-onlyIdempotent

Find the Learn article, glossary term, calculator or research page that answers an options question: strategies, the greeks, implied volatility, IV rank, probability of profit, rolling, assignment, the wheel, screening rules and more. Returns titles, summaries and links.

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": {
      "query": "<query>"
    },
    "name": "learn_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results, 1 to 20. Default 5.
queryYesWhat to look for, in plain words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / query / maxLength
      Added value: +200
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. Beyond that, the description adds real value with 'Returns titles, summaries and links', which is the only source of return-shape information since there is no output schema. It stops short of explaining relevance ranking or whether results are clipped by the limit.

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?

Two sentences, front-loaded with the action and resource, with every clause earning its place — the topic list does real work by signalling achievable queries and the final clause supplies the return format. Nothing is redundant with the title or annotations.

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?

For a two-parameter, read-only, non-destructive search with no output schema, the description covers corpus scope and return shape well, which is what an agent needs to call it. The remaining gaps — result ordering, whether the limit truncates rather than paginates, and the handoff to learn_read — are small but real.

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%: the schema explains that query is 'what to look for, in plain words' and that limit is 1 to 20 with a default of 5. The description adds nothing about query formulation beyond what the schema states, though its enumeration of topics (greeks, IV rank, the wheel, screening rules) gently hints at what vocabulary works. Baseline 3 applies when the schema carries the parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb (find) applied to a specific resource (the Learn library of articles, glossary terms, calculator pages and research pages), and enumerates the topical domains covered. The closing clause 'Returns titles, summaries and links' also makes clear this is a documentation lookup rather than a computation, which separates it from the calculator-style siblings.

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?

Usage is implied by the framing 'answers an options question', which tells the agent the right context for calling it. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of following up with learn_read to fetch the full article, and no warning that computational questions should go to siblings like profit_calculator or probability_of_profit.

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