Skip to main content
Glama

LrrK Agent Desk

Find public LrrK evidence

lrrk_find_evidence
Read-onlyIdempotent

Search published LrrK Letters, reviewed Hardware Attack Library records, and admitted Intelligence Product metadata. Returns bounded excerpts and canonical source links. Historical paid publication bodies are never returned.

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": {
      "query": "<query>"
    },
    "name": "lrrk_find_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
corpusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 genuinely new behavioral context — bounded excerpts, canonical source links, and a firm exclusion that historical paid publication bodies are never returned. That content-restriction note is exactly the kind of non-obvious behavior an agent needs. It does not mention pagination or how bounding is applied, keeping it short of a 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?

Three short sentences with no filler, front-loaded with the scope and followed by return shape and the exclusion. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description usefully sketches what comes back (bounded excerpts, canonical links). However, for a three-parameter search tool with zero schema description coverage, the missing explanation of query matching behavior and the limit ceiling leaves a real gap in what an agent needs to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning, and it largely does not. Only the corpus dimension is indirectly explained ("Letters", "Hardware Attack Library", "Intelligence Product"), while query semantics and the limit parameter — including a hard maximum of 10 and a 120-character query cap — are never mentioned. An agent could pass limit=50 and only learn from the schema or a validation error.

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 names a specific verb ("Search") plus three enumerated resource types — published LrrK Letters, reviewed Hardware Attack Library records, and admitted Intelligence Product metadata — which lets an agent distinguish this retrieval tool from siblings like lrrk_get_evidence without opening a schema. It stops short of explicitly contrasting against those siblings, so it is clear but not fully differentiated.

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: the agent can infer this is the broad discovery/search entry point versus a get-by-id tool, but the description never states when to prefer it over lrrk_get_evidence or lrrk_find_service. The enumeration of three corpora loosely maps to the corpus enum, giving a hint about scoping but no explicit guidance on choosing a corpus.

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