Skip to main content
Glama
Sign In

Valeur Intrinsèque

by fr.valeur-intrinseque.mcp
OverviewDiscussionsAdmin

screen_stocks

Recently analyzed stocks ranked by Score VI, highest first. Returns ticker, name, score and price. Does not filter by country, region or sector, and does not return a per-share intrinsic value. Not counted in the Score VI quota.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "screen_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (default: 20, max: 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Nombre de résultats (défaut : 20, max : 50)"New value: +"Number of results (default: 20, max: 50)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/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 does fairly well: it discloses the sort order, the returned fields, the lack of filtering, and a genuinely useful quota note ('Not counted in the Score VI quota'). It does not cover pagination behavior beyond the max limit or any auth requirements, but for a read-only listing tool the coverage is solid.

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?

Three short sentences, front-loaded with what it does and what it returns before the caveats. No redundant or filler sentences, though the inline negatives could be compressed into one clause.

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?

No output schema exists, and the description correctly compensates by enumerating the returned fields and sort order. It also flags the quota behavior and filtering limits. The only gap is pagination/results-window behavior beyond the limit parameter, which is minor for a single-parameter screen.

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% – the single 'limit' parameter is fully documented with default (20) and max (50) in the schema. The description adds nothing about 'limit', so the baseline 3 applies; the schema does the heavy lifting.

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 and resource ('Recently analyzed stocks ranked by Score VI, highest first') and enumerates the returned fields (ticker, name, score, price). The explicit negatives (no country/region/sector filter, no per-share intrinsic value) further sharpen what it is against siblings like get_intrinsic_value.

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

Usage Guidelines3/5

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

The exclusion statements ('Does not filter by country, region or sector', 'does not return a per-share intrinsic value') implicitly steer the agent away for filtered or intrinsic-value needs, but no sibling is named and no explicit 'use X instead when Y' guidance is given. Usage is inferred rather than stated.

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