Manawa Terminal

Create screener

create_screener

Save a screener filter query for scheduled enter/exit (joiner/leaver) notifies.

Same rows as Terminal Save on /screener. Pass last_symbols (current matches)
or call run_screener after create to seed the baseline; later runs notify
names that enter or leave when Settings Screener in & out is on.

Args:
    name: Screener name (blank → derived from filters)
    query: Filter blob {universe, fmp, metrics, ai, member?, view?}
    schedule: "off", "daily", or "weekly" (weekly requires Pro)
    notify_on_change: Notify on enter/exit after the first seed (default true)
    last_symbols: Current result tickers to seed the enter/exit baseline

Input Schema

Name	Required	Default
`name`	No
`query`	No
`schedule`	No	off
`last_symbols`	No
`notify_on_change`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations only declare the generic write profile (readOnlyHint=false, destructiveHint=false), so the description carries extra weight and delivers: "weekly requires Pro" is a real entitlement constraint, and the notify-on-change seeding behavior explains the side effects after creation. It does not describe what the returned object contains, though an output schema exists to cover that.

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?

Purpose is front-loaded in one sentence, followed by a short usage paragraph and a scannable Args block. A few phrases are product jargon ("Same rows as Terminal Save on /screener") but nothing is padding; the length is justified by five undocumented parameters.

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 zero-required-parameter create tool with an output schema, it covers the essentials: entitlement gating, the baseline-seeding workflow, and notification semantics. Minor gaps remain around how the query blob's sub-keys are interpreted and whether re-creating a duplicate name is allowed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must do all the work and it does: it documents every one of the five parameters, including allowed schedule values, the blank-name fallback, the notify_on_change default, and the query blob's key structure. This is exactly the compensation the low coverage requires.

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 first sentence names a concrete verb and resource ("Save a screener filter query") and adds the specific purpose (scheduled enter/exit notifies). It implicitly separates itself from run_screener by referencing it as a follow-up step, but it never explicitly contrasts with update_screener, so sibling differentiation is left partly to inference.

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?

It gives real operational guidance: seed the baseline either by passing last_symbols or by calling run_screener after create, and it notes the feature only fires when Settings Screener in & out is on. It stops short of stating when to create a new screener versus update an existing one, which is the obvious adjacent alternative.

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

All Manawa Terminal 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?