Skip to main content
Glama
Sign In

Valeur Intrinsèque

by fr.valeur-intrinseque.mcp
OverviewDiscussionsAdmin

get_price_history

Price-history summary for one ticker: first and last price, change, high, low, and the last 10 points. Not counted in the Score VI quota.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_price_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNoHistory window (default: 1y)1y
symbolYesStock ticker (e.g. AAPL)
intervalNoBar interval (default: 1d)1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / interval / description
      Previous value: -"Intervalle (défaut : 1d)"New value: +"Bar interval (default: 1d)"
    • changedInput schema / properties / range / description
      Previous value: -"Période (défaut : 1y)"New value: +"History window (default: 1y)"
    • changedInput schema / properties / symbol / description
      Previous value: -"Ticker boursier (ex: AAPL)"New value: +"Stock ticker (e.g. AAPL)"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the response payload (first/last price, change, high, low, last 10 points). It says nothing about truncation limits beyond 'last 10 points', adjustment conventions, caching, rate limits, or auth requirements, leaving material behavior undisclosed.

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?

Two sentences, with the substantive return-shape information front-loaded and dense. The trailing quota remark is irrelevant noise to a calling agent, but the overall size is tight and non-redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, so the description must cover returns – and it does list the key fields. However, it omits what 'change' denotes (absolute vs percent), price basis (adjusted vs raw), and the meaning of the 10-point truncation, leaving real gaps for a data tool.

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

Parameters3/5

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

Schema description coverage is 100% – symbol, range, and interval all carry descriptions, defaults, and enums in the schema. The description addresses only the 'one ticker' constraint and adds no meaning about range/interval interactions, so the baseline 3 applies.

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?

States a specific verb and resource ('price-history summary for one ticker') and enumerates the returned fields, which lets an agent distinguish it from get_stock_price's single-point read. It never names the sibling it competes with, so the differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no statement of when to use this over get_stock_price, compare_stocks, or screen_stocks, and no prerequisites or exclusions. The second sentence ('Not counted in the Score VI quota') is unrelated scoring metadata and gives the agent no invocation guidance.

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

All Valeur Intrinsèque toolsInspect
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