Skip to main content
Glama

Valeur Intrinsèque

get_moat_score

Cached competitive-advantage (moat) score from 1 to 5 for one ticker. 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_moat_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesStock ticker or company name (e.g. AAPL, LVMH)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden and does disclose two useful traits: results are cached and the call does not consume the Score VI quota. It omits staleness/refresh behavior, error handling for an unknown ticker, and the shape of the returned value beyond the 1–5 scale.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with what is returned and followed by the quota caveat. Nothing redundant or 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 one-parameter cached read with no output schema, the definition covers what is returned, its scale, its caching nature, and its quota cost — enough for an agent to call it correctly. Only staleness and failure modes are left unstated.

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 coverage is 100% on the single 'symbol' parameter, so the schema already defines accepted input. The description only reinforces the one-ticker-per-call scope, adding no format or edge-case detail beyond what the schema states.

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 resource and return scale: 'Cached competitive-advantage (moat) score from 1 to 5 for one ticker.' The resource name ('moat score') inherently separates it from siblings like get_management_score, but it never explicitly contrasts with them, so it stops short of a 5.

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 line 'Not counted in the Score VI quota' is a genuine usage signal — it tells an agent this call is cheap relative to quota-consuming siblings. However, there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for fresh (non-cached) computation.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources