Skip to main content
Glama

LrrK Agent Desk

Map public evidence coverage

lrrk_map_coverage
Read-onlyIdempotent

Map a topic and optional device class to reviewed public references and explicit gaps. Search matches are not device-specific applicability, testing, or risk verdicts.

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": {
      "topic": "<topic>"
    },
    "name": "lrrk_map_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes
deviceClassNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds real behavioural context by framing output as reviewed references plus explicit gaps and by warning that search matches are not applicability, testing, or risk verdicts. It still leaves open how a "gap" is determined and whether results are ranked or paginated, which is why it stops short of 5.

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 tight sentences: the operation and its output are front-loaded, and the caveat follows immediately with no filler. Every clause carries information.

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 simple two-parameter, read-only lookup with no output schema, the description supplies the shape of the return (references plus gaps) and an important interpretive caveat. The main remaining gap is the meaning of "reviewed" and how gaps are represented, which is minor for a tool this simple.

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?

With 0% schema description coverage the description carries the burden, and it does identify both parameters plus the fact that deviceClass is optional. However, it gives no sense of what a valid topic string looks like or what vocabulary deviceClass expects, so the schema's bare maxLength/minLength constraints remain the only documentation.

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 pairs a specific verb ("Map") with a specific output resource ("reviewed public references and explicit gaps") and the two inputs, which is far clearer than a restatement of the name. It does not name or contrast with any sibling such as lrrk_find_evidence or lrrk_get_evidence, so an agent must infer the division of labour.

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?

Usage is only implied through the stated result (coverage plus gaps), which suggests use when assessing what evidence exists for a topic-device pair. There is no explicit "use this when" or "use X instead" routing, and the second sentence is a disclaimer about interpretation rather than guidance on tool selection.

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