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 / cost_usd / properties / basis / descriptionPrevious value: -"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."New value: +"payg_charge = real pay-per-call charge (a card or MPP payment through agent-pay). payg_rate_card = indicative price, not billed."Output schema / properties / _meta / properties / cost_usd / properties / basis / descriptionPrevious value: -"payg_charge = real agent-pay charge. payg_rate_card = indicative price, not billed."New value: +"payg_charge = real charge (agent-pay or your balance). payg_rate_card = indicative price, not billed."Output schema / properties / _meta / properties / cost_usd / properties / billed / descriptionPrevious value: -"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value; your plan already covers this call for free."New value: +"true = this amount was actually charged via PAYG for this call. false = indicative PAYG-equivalent value only: no charge was made for this call (it was within your plan)."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 read-only, idempotent, closed-world and non-destructive, so the safety profile is settled. The description earns credit for adding behavior the annotations don't: what is returned (full ticker set + criteria), the NOT_FOUND failure mode for unknown names, and a tier requirement with 'sample rejected'. Rate limits and privacy scoping ('this user') are only lightly implied.
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?
Three compact clauses with zero waste; the core purpose and the name-not-id constraint are front-loaded, and the error/tier caveats follow in descending priority.
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?
An output schema exists so return shape needn't be spelled out, and the description still summarizes it. For a one-parameter read with a tier gate and a single documented error case, nothing an agent needs to call it correctly is missing.
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?
The single parameter is fully documented in the schema (case-insensitive, 1–80 chars), so the baseline is 3. The description adds a genuine semantic point beyond the schema: the key is a name, not an id, and it is inherently case-insensitive, which tells the agent how to construct the call correctly.
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?
States a specific verb and resource (fetch a single watchlist) and pins the scope precisely: full ticker set + criteria, keyed by name rather than id. That distinguishing detail separates it from list_watchlists and from any id-based retrieval without needing the schema.
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 'by its name, not an id' phrasing and the NOT_FOUND note imply the correct usage context, and the tier line gates access. However, no sibling is named explicitly (list_watchlists, watchlist_diff, delete_watchlist), so the agent must infer the routing itself.
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.