Skip to main content
Glama

DilutionLens

by com.dilutionlens
OverviewDiscussionsAdmin

Screen

screen
Read-onlyIdempotent

Screen the ASX universe by dilution risk, cash cover, market cap industry or mining commodity and stage. Returns at most 20 rows — always the top of the requested ordering; there is no offset paging. A discovery tool, not an extract. Filters: q (name/ticker search), risk, cover, cap, industry, commodity, stage, suspended, sort, dir. Companies suspended from official quotation are EXCLUDED by default, the same as on the website; suspended_hidden in the response says how many this query withheld and suspended=include returns them.

Input Schema

NameRequiredDescriptionDefault
qNoName or ticker search
capNonano | micro | small | mid | large | na
dirNoasc | desc
riskNoVery high | High | Moderate | Low | Minimal | Not rated
sortNorisk | dilution | cover | mktcap | raises | ticker | name | industry | itm | pending | expiry | short
coverNo<2q | 2-4q | 4+q | na
stageNoStage of the company's most advanced project on that commodity: Exploration | Resource | Reserve | Scoping Study | Pre-Feasibility Study | Definitive Feasibility Study | FID | Production | Past Producer
industryNoGICS industry group, exact name as the site shows it, e.g. Materials, Energy, Software & Services, Pharmaceuticals, Biotechnology & Life Sciences
commodityNoPrimary commodity of a mining or energy company, lower case, e.g. gold, copper, lithium, uranium, rare earths
suspendedNoinclude — return companies suspended from official quotation, which are excluded by default

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / commodity
      Added value: +{
+  "description": "Primary commodity of a mining or energy company, lower case, e.g. gold, copper, lithium, uranium, rare earths",
+  "type": "string"
+}
    • addedInput schema / properties / stage
      Added value: +{
+  "description": "Stage of the company's most advanced project on that commodity: Exploration | Resource | Reserve | Scoping Study | Pre-Feasibility Study | Definitive Feasibility Study | FID | Production | Past Producer",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the readOnly/idempotent annotations by disclosing the hard 20-row cap, the absence of offset paging, that results are the top of the requested ordering, and the suspended-quotation exclusion policy. The `suspended_hidden` response field lets the agent detect and reason about withheld rows rather than silently under-reporting.

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 purpose, then behavior, then filters — the right order. Minor filler: "the same as on the website" and the trailing filter-name list duplicate what the schema already shows.

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?

With no output schema and 10 optional params, the description supplies the two things an agent most needs: the result cap and the suspension default. It omits the default sort/ordering and any note on result cost, which would round out a discovery tool.

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 schema carries most parameter meaning. The description still adds real semantics for `suspended` (default exclusion, the `include` value, and its effect on the response) and for `q`; the remaining names are only restated.

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?

Specific verb plus resource ("Screen the ASX universe") with the exact filter dimensions enumerated. The line "A discovery tool, not an extract" cleanly separates it from the get_* siblings, which are single-entity lookups.

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?

The discovery-vs-extract framing tells the agent when this tool is the right first move rather than going to a detail tool. It stops short of naming a specific sibling or stating when to follow up with get_dilution_snapshot / get_cash_runway.

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

All DilutionLens 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