Qanvo Stock Screener

Browse example screens

browse_examples

Read-onlyIdempotent

Browse Qanvo's library of tested example screens (the same ones as https://qanvo.app/examples): ready-made plain-English questions for options sellers and buyers, value, growth, dividends, momentum, technicals, insiders, Congress trades, ETFs, crypto, and markets outside the US. Use it when the user asks what they can screen for, wants ideas, or names a strategy without the details. With no arguments: the categories and how many examples each has. With search (words such as "covered call" or "dividend growth"; every word must match) and/or category (a category name, or "all"): the matching examples with title, prompt, description and page link. To run one, call market_query with its prompt exactly as given and no market: it then runs from a pre-planned version, instantly. Research ideas only, not investment advice.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_examples"
  }
}

Input Schema

Name	Required	Description	Default
`search`	No	Optional words to search for in the title, prompt, description and category.
`category`	No	Optional category name (e.g. "Premium Sellers", "Dividend & Income", "India"), or "all" for every example.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world browse operation. The description adds behavior beyond annotations: no-argument output is categories and counts; search requires every word to match; results include title, prompt, description and page link; and examples run instantly through market_query from a pre-planned version. It also adds the research-only disclaimer.

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?

The description is front-loaded and organized around no-argument, search/category, and run-one behavior. It is dense rather than bloated, and the long list of covered domains earns its place by showing scope. Some sentences are run-on and could be split, but there is little wasted content.

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?

There is no output schema, but the description explains the return shape for both modes: categories with counts when no arguments are supplied, and matching examples with title, prompt, description and page link when searching or filtering. It also covers how to act on a result, so the definition is complete for this two-parameter browse tool.

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 both parameters. The description still adds useful meaning: no arguments returns categories and counts; search words must all match; search and category can be combined; and category accepts a name or 'all'. The added matching semantics are valuable, though the schema already carries most parameter details.

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 uses a specific verb and resource: browsing Qanvo's library of tested example screens. It clearly distinguishes this from market_query by explaining that browse_examples is for discovering examples, while market_query is for running one. The agent can identify the tool's role without opening the schema.

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

Usage Guidelines5/5

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

It gives explicit triggers: user asks what they can screen for, wants ideas, or names a strategy without details. It also names the alternative and the exact routing condition: to run an example, call market_query with its prompt exactly as given and no market. No inference is needed about when to use this vs the sibling.

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

All Qanvo Stock Screener 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?