Skip to main content
Glama

LrrK Agent Desk

Get a cited public record

lrrk_get_evidence
Read-onlyIdempotent

Retrieve the metadata, edition, citations, evidence status and limits for one public LrrK record. A historical Intelligence Product returns metadata and its exact-edition owner handoff only.

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": {
      "kind": "<kind>",
      "id": "<id>"
    },
    "name": "lrrk_get_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral context beyond them by disclosing a partial-result case: a historical Intelligence Product returns metadata and its exact-edition owner handoff only. It does not cover not-found behavior or whether the record shape varies by kind, which keeps it below 5.

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?

Two tight, front-loaded sentences that lead with the retrieval scope and then attach the conditional caveat. The phrase "exact-edition owner handoff" is dense internal jargon that costs some clarity, but there is no filler.

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?

With no output schema, the description does useful work by naming the returned fields and the Intelligence Product special case. However, for a two-required-parameter lookup it omits kind-value semantics and error/empty-result behavior, which an agent needs to invoke 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 the load, and it largely does not. It never explains the `id` parameter (scope, uniqueness, whether it is kind-qualified) and only obliquely gestures at the `kind` enum through the phrase "Intelligence Product", leaving "hal" and "letters" completely undefined.

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?

States a specific verb ("Retrieve") and a specific resource ("one public LrrK record") and enumerates the returned facets: metadata, edition, citations, evidence status and limits. It is implicitly distinguishable from a search-style sibling by the singular "one ... record" scope, but it never names or contrasts an alternative, so it falls short of a 5.

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: an agent can infer this is a single-record lookup keyed by kind+id rather than a search. There is no explicit when-to-use, when-not-to-use, or pointer to lrrk_find_evidence for discovery, and no statement of prerequisites, so guidance is minimal.

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