Skip to main content
Glama

LrrK Agent Desk

Find a LrrK review path

lrrk_find_service
Read-onlyIdempotent

Find LrrK's human-reviewed Assess, Engage, Monitor, or one-question Evidence Brief path for a stated need. Returns criteria and a first-party link; no inquiry is submitted and no work is initiated.

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": {
      "need": "<need>"
    },
    "name": "lrrk_find_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYes

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 the safety profile is covered. The description adds real value beyond that: it states what comes back (criteria and a first-party link) and explicitly that no inquiry is submitted and no work is initiated, which is exactly the reassurance an agent needs before calling a discovery tool.

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 sentences, no filler. The purpose is front-loaded and the behavioral caveat (no inquiry submitted) follows immediately, so nothing needs to be skimmed for.

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 read-only lookup with no output schema, the definition supplies purpose, return shape, and a clear non-commitment guarantee. The only remaining gap is what each enum value selects, which would have made it fully self-contained.

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 description coverage is 0%, and the single parameter is a five-value enum whose terms (device-risk, authorized-test, change-monitoring, unsure) are not self-explanatory. The description mentions "a stated need" and lists path names, but does not map enum values to outcomes, so it only partially compensates for the 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?

"Find LrrK's ... path for a stated need" gives a specific verb and resource, and the named path types (Assess, Engage, Monitor, Evidence Brief) distinguish it from evidence-retrieval siblings like lrrk_get_evidence. It stops short of explicitly contrasting itself with any sibling, so an agent must infer the boundary from wording alone.

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?

"For a stated need" and "no inquiry is submitted and no work is initiated" imply this is a routing/lookup step rather than a retrieval or action step, which is useful context. However, there is no explicit when-to-use versus lrrk_find_evidence or lrrk_map_coverage, and no when-not guidance, leaving the choice among siblings to inference.

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