mcp.xynaptic

security-price

Xynaptic Security Price — spot market data for US stocks: price, previous close, day range, 52-week range, currency, exchange + up to 30d history (OHLCV). GET ?ticker=AAPL&history=30. Refreshed intraday. Usage: Use for a US-listed stock price with optional history. EU-listed stocks are available through the xynaptic-catalog tool (security-eu-price and siblings). [price: $0.010 per call, x402/USDC]

Input Schema

Name	Required	Description	Default
`params`	Yes	query parameters

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 3, 2026
- changedInput schema / properties / params / properties / ticker / description
```
Previous value: -"example: \"AAPL\""New value: +"required. example: \"AAPL\""
```
- addedInput schema / properties / params / required
```
Added value: +[
+  "ticker"
+]
```
- changedInput schema / required
```
Previous value: -[]New value: +[
+  "params"
+]
```

Changed4 schema fields changedOct 2, 2026

removedInput schema / properties / body

Removed value: -{
-  "description": "JSON body for POST endpoints (e.g. insurance, ai-chat, production-risk)",
-  "type": "object"
-}

changedInput schema / properties / params / description

Previous value: -"query parameters, e.g. {city: 'Paris', type: 'Appartement'}"New value: +"query parameters"

addedInput schema / properties / params / properties

Added value: +{
+  "previous_close": {
+    "description": "example: 336.13",
+    "type": "number"
+  },
+  "price": {
+    "description": "example: 341.07",
+    "type": "number"
+  },
+  "ticker": {
+    "description": "example: \"AAPL\"",
+    "type": "string"
+  },
+  "week52_high": {
+    "description": "example: 345.34",
+    "type": "number"
+  },
+  "week52_low": {
+    "description": "example: 169.21",
+    "type": "number"
+  }
+}

addedInput schema / required
```
Added value: +[]
```

First observedOct 1, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does substantial work: it discloses freshness ('Refreshed intraday'), the data sources composition (price/close/ranges/currency/exchange/OHLCV), the history cap (up to 30d), and — unusually — the cost and payment rail ('$0.010 per call, x402/USDC'), which matters for an agent deciding whether to invoke. It does not state error behavior for invalid tickers or rate limits, so it falls short of a 5.

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?

Front-loaded with the tool's identity and payload, then invocation example, freshness, usage/exclusion, and pricing. Every clause earns its place except the pricing tag, which could arguably live in structured metadata. It is dense but not padded.

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 single-required-param fetch tool with no output schema, the description supplies exactly what an agent needs: what comes back, freshness, a call example, the domain boundary (US-only), the sibling route for EU, and cost. The only omissions are error/rate-limit behavior, which is minor given the tool's simplicity.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the 'history=30' example gives the syntax and semantics of a history parameter (value = number of days, max 30) that is not in the schema, and the 'ticker=AAPL' example confirms the expected format. The stray price/previous_close/week52 fields in the schema are output-like, not user parameters, and the description clarifies the tool is invoked by ticker + history.

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?

States a specific verb/resource ('Security Price — spot market data for US stocks') and enumerates exactly what is returned: price, previous close, day range, 52-week range, currency, exchange, plus 30d OHLCV history. It explicitly excludes EU-listed stocks and points to the sibling tool (xynaptic-catalog → security-eu-price), so an agent can distinguish it from commodity-price, crypto-price, and property-price without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('Use for a US-listed stock price with optional history') and an explicit when-not-to-use with the alternative named ('EU-listed stocks are available through the xynaptic-catalog tool'). It even provides a concrete invocation example (GET ?ticker=AAPL&history=30). Nothing is left to inference.

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

All mcp.xynaptic tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?