Skip to main content
Glama

Metis — Preview Focus Lens

preview_focus_lens

Test a lens before creating a focus by comparing match counts for each keyword group alone and combined, revealing which group causes zero results.

Instructions

Try a lens before creating a focus — how much does it catch, and where does it fail?

Lens tuning was otherwise blind: the only way to learn a lens returned nothing
was to build the focus, open it and find it empty. Worse, a conjunction that
returns zero says nothing about WHICH group is at fault.

So this reports each group's matches ALONE as well as combined. If group 1
matches 400 and group 2 matches 3 and together they match 0, group 2 is the
problem and no judgement is required to see it.

Args:
    keyword_groups: JSON list of lists — OR within a group, AND across groups.
        e.g. '[["malaria","plasmodium"],["elimination","surveillance"]]'

Returns:
    Per-group and combined counts, sample matches, and a plain verdict.

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": {
      "keyword_groups": "<keyword_groups>"
    },
    "name": "preview_focus_lens"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyword_groupsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden — and it does most of the work: the word 'preview/try' plus 'before creating a focus' establishes this is a dry run that does not persist anything. It also discloses that it returns per-group AND combined counts, samples, and a verdict. It doesn't explicitly promise read-only/no side effects or discuss cost, which a mutation-adjacent tool could.

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 core purpose and the diagnostic payoff are front-loaded, and the Args/Returns blocks are tight. The middle rationale paragraph ('Lens tuning was otherwise blind…') is a bit of narrative that could be trimmed, but it does convey the concrete per-group insight the tool provides.

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?

With an output schema present, return values needn't be spelled out, yet the description still summarizes them. The single parameter is fully documented in prose despite zero schema coverage, and the failure-diagnosis behavior is explained. Nothing an agent needs to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 0% (the lone parameter is an untyped string with no description), yet the description fully compensates: it explains the nested list-of-lists structure, states OR-within-group / AND-across-groups semantics, and supplies a concrete JSON example. An agent could construct a correct argument from the description alone.

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 verb and resource ('Try a lens before creating a focus') and states its two outputs — match volume and failure location. It clearly separates itself from the act of creating a focus, though it never names the actual sibling tool (create_focus_area) that follows it.

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 gives a clear trigger ('before creating a focus') and a diagnostic trigger (a conjunction returning zero, where you need to know which group is at fault). It does not explicitly say when NOT to use it or name create_focus_area as the alternative, but the intended workflow stage is unambiguous.

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

Deploy Server

Other Tools