Skip to main content
Glama
screener-mcp
by LogeshR15

get_moat_signals

Read-only

Quantify a company's moat using revenue share, industry concentration, ROCE consistency, margin stability, sales CAGR, and promoter-holding signals.

Instructions

Quantitative moat proxies for a company — market position plus how durable its economics have been.

Market position (from every listed company in its Screener industry): revenue share and rank by quarterly sales, industry concentration (HHI and CR4 — fragmented / moderately / highly concentrated), market-leader and top-3 flags. Durability (from up to ~12 years of statements): ROCE consistency (years ≥ 15%, median, min), operating-margin stability (standard deviation), sales CAGR, promoter-holding stability. Plus a signals summary with the thresholds used.

These are proxies — listed-company revenue share misses unlisted and imported competitors, and brand / switching costs / licences still need judgement (check the annual report and earnings calls).

symbol: NSE/BSE symbol or company name

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_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond readOnlyHint and openWorldHint, it discloses data sources and scope: listed-company revenue share within the Screener industry, HHI/CR4, up to ~12 years of statements, ROCE/margin/CAGR metrics, and a thresholds summary. It also states concrete limitations (unlisted/imported competitors are missed; qualitative moat factors need separate judgement), which is exactly the extra behavioral context an agent needs.

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 definition is front-loaded with purpose, then separates market-position, durability, caveat and parameter sections in a scannable way. It is longer than a minimal description, but nearly every line carries methodology or limitation information; only light trimming would improve it.

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?

An output schema exists, so the description need not explain return values, and the annotations already establish read-only/open-world behavior. Given the tool's analytical complexity, the description supplies enough methodology, scope and input guidance for an agent to invoke it correctly.

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?

The schema gives only 'symbol' as a string with no description, so the description's 'NSE/BSE symbol or company name' adds necessary meaning about accepted input. It does not add examples or matching rules, but for a single parameter it substantially closes the 0% schema-coverage gap.

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?

The description opens with a specific resource: quantitative moat proxies covering market position and economic durability. It is clearly not a general financials or peer tool, but it never names a sibling to contrast with, so sibling routing relies on inference.

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 frames the tool as a proxy-based moat assessment and warns that brand, switching costs and licences require annual-report/earnings-call judgement. That gives clear context for when the output is useful and where it is insufficient, though it does not explicitly point to an alternative sibling tool or state exclusions.

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