Levelset by StandPoint

Everything about one name

ticker_profile

Read-onlyIdempotent

Everything the desk knows about one ticker, in one call, the way the ticker page shows it: last close and returns, the 52-week range and drawdown, the desk's reversion score and own beta, the desk's written view when there is one, the next earnings report with its consensus and history, fundamentals (valuation, margins, growth, balance sheet, dividend, analysts) each ranked against the book, the themes the name belongs to, whether it is an open pick (with publishedAt, priceAtPublish, target and stop) or on this member's watchlist, and the full levels: pivot zones plus the daily, weekly and monthly opens, sigma bands and 50/100/200 EMAs. Use this before answering any question about a specific stock. Answers any account, free included. Europe names carry a venue suffix (AIR.PA) and return price, levels and the pick; fundamentals are not held for them yet.

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": {
      "ticker": "<ticker>"
    },
    "name": "ticker_profile"
  }
}

Input Schema

Name	Required	Description	Default
`ticker`	Yes	A ticker, e.g. NVDA or AIR.PA.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already establish that this is a safe read-only, idempotent, non-open-world operation. Beyond that, the description discloses the substantive behavioral context: it is a single-call profile, covers all account tiers, and has an important Europe limitation where fundamentals are not held.

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 core purpose and usage rule are front-loaded, and the enumerated contents are relevant because there is no output schema. The first sentence is nevertheless very long and run-on, so it is informative but not maximally concise.

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?

For a complex, high-content tool with no output schema, the description carries the return-value burden well: it lists the major data groups, the levels detail, pick/watchlist status fields, and the Europe coverage caveat. Nothing critical to deciding whether to call it appears missing.

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 useful parameter meaning by stating that Europe names require a venue suffix such as AIR.PA, which goes beyond the schema's simple example and helps avoid malformed tickers.

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 resource and scope: everything the desk knows about one ticker in one call, then enumerates the included data classes. An agent can distinguish it from narrower siblings like levels_get or screen because this is explicitly the all-in-one ticker profile.

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 a clear usage rule: use this before answering any question about a specific stock, and notes that it works for any account including free accounts. It does not explicitly name when to prefer siblings such as levels_get for only levels or screen for discovery, so it stops short of full alternative routing.

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

All Levelset by StandPoint 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?