Qanvo Stock Screener

Refine a screen

refine_market_query

Read-only

Modify a previous market_query result (e.g. 'only semiconductors', 'add IV rank and sort by it'). Keeps the prior filters unless the instruction changes them.

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_id": "<query_id>",
      "session_id": "<session_id>",
      "instruction": "<instruction>"
    },
    "name": "refine_market_query"
  }
}

Input Schema

Name	Required	Description
`market`	No	Optional market (ISO country code); use the same one as the query being refined.
`query_id`	Yes	query_id of the result to refine.
`session_id`	Yes	session_id of that result.
`instruction`	Yes	The refinement in plain English.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The annotations already declare this is a non-destructive read-only operation. The description adds useful behavioral context by explaining that prior filters are retained unless the instruction overrides them, which is not captured in the annotated safety profile.

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?

The description is two tight sentences with no filler. The core operation is front-loaded, followed immediately by the key persistence rule.

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 refinement tool with full schema descriptions and safety annotations, the definition covers the core operation and filter-retention behavior. It does not describe the return shape or whether the refined result gets a new query_id, but the absence of an output schema makes this a smaller gap.

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 description coverage is 100%, so the baseline is 3. The description adds value by illustrating the kind of plain-English refinement expected in the instruction parameter, such as 'only semiconductors' or 'add IV rank and sort by it'.

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 and resource: modify a previous market_query result. It also gives concrete examples of valid refinements, making clear how this differs from creating a new screen with market_query.

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 usage context is clear: this tool is for refining an existing market_query result, and the prior filters are preserved unless the instruction changes them. It does not explicitly state when to use market_query instead, but the reference to a prior result implies the alternative.

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?