get_watchlistFetch a single watchlist (full ticker set + criteria) by its name, not an id (case-insensitive). NOT_FOUND if the name is unknown to this user. Tier: sp500+ (sample rejected).
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Watchlist name to fetch (case-insensitive, 1–80 chars). |
| Name | Required | Description | Default |
|---|---|---|---|
| _meta | Yes | Provenance envelope — data lineage for every MCP response | |
| watchlist | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / _meta / properties / fundamentals_as_of / descriptionPrevious value: -"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to."New value: +"ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt in bulk. Use THIS — not `last_updated` — when telling a user how current the cross-sectional fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to. It is a floor for a single filer, not a ceiling: a filer with a live partition receives its filing, facts and ratios intraday (minutes after EDGAR dissemination), so an entity-scoped read may carry a filing newer than this; cross-sectional ranks (factor scores, earnings signals) refresh with the weekly bulk export."Output schema / properties / watchlist / properties / weightsAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+}Output schema / properties / _meta / properties / fundamentals_as_ofAdded value: +{
+ "description": "ISO timestamp when the FINANCIAL STATEMENTS were last rebuilt. Use THIS — not `last_updated` — when telling a user how current the fundamentals are. The snapshot is republished on every weekday price refresh while the statements are carried forward unchanged, so `last_updated` can be far more recent than the numbers it sits next to.",
+ "type": "string"
+}Output schema / properties / _meta / properties / price_as_ofAdded value: +{
+ "description": "ISO timestamp when the price surfaces were last refreshed.",
+ "type": "string"
+}Output schema / properties / _meta / properties / cost_usdAdded value: +{
+ "additionalProperties": false,
+ "description": "Per-call cost transparency. Omitted for subscription-only tools that have no PAYG-equivalent price.",
+ "properties": {
+ "amount_usd": {
+ "minimum": 0,
+ "type": "number"
+ },
+ "basis": {
+ "description": "payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed.",
+ "enum": [
+ "payg_charge",
+ "payg_rate_card"
+ ],
+ "type": "string"
+ },
+ "billed": {
+ "description": "true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "amount_usd",
+ "billed",
+ "basis"
+ ],
+ "type": "object"
+}Output schema / properties / _meta / properties / latency_msAdded value: +{
+ "description": "Wall-clock milliseconds this tool call took, measured server-side around the handler.",
+ "minimum": 0,
+ "type": "integer"
+}Output schema / properties / _meta / properties / pit_safe / descriptionAdded value: +"true iff a zero-look-ahead point-in-time cut was applied to every returned figure"Input schema / properties / name / descriptionAdded value: +"Watchlist name to fetch (case-insensitive, 1–80 chars)."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover readOnly, idempotent, and non-destructive behavior, so the description needs to add beyond that. It discloses user-scoped visibility ('unknown to this user'), case-insensitive matching, NOT_FOUND behavior, tier access restriction, and that the result includes both tickers and criteria. This is rich, non-redundant behavioral context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is three tight sentences with no filler. The core action is front-loaded, followed by the key lookup behavior and then access constraints. Every sentence earns its place and adds information an agent needs.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a single parameter, full schema coverage, rich annotations, and an output schema, the description covers all essential behavioral details: what is fetched, how lookup works, error behavior, user scoping, and tier restriction. There are no significant gaps for an agent to call this tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% and the name parameter is well-described in the schema, so the baseline is 3. The description adds meaningful semantics by clarifying that the name itself is the lookup key, not an id, and that lookup is case-insensitive. This goes slightly beyond the schema's parameter description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Fetch'), a specific resource ('a single watchlist'), and the key content ('full ticker set + criteria'). It also distinguishes this tool from any ID-based lookup by explicitly saying 'by its name, not an id,' which separates it from other get/list siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives strong usage context: fetch by name rather than id, case-insensitive matching, and NOT_FOUND behavior when the name is unknown to the user. It also communicates an access restriction ('Tier: sp500+'). It does not explicitly name an alternative like list_watchlists for enumerating watchlists, but the usage boundary is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.