Skip to main content
Glama

lurq

by io.github.jadenryu
OverviewDiscussionsAdmin

Version-exact API surface + drift

usage
Read-only

A package version's TYPED API: exported symbols and their signatures from its shipped .d.ts (or DefinitelyTyped), exact to the version, none of it in the model's training data. Use before writing code against a package whose API may have moved. For whether a name exists at RUNTIME (what decides if an import throws) use resolve_surface; for is-it-safe-to-install use verify. Pass knownVersion (e.g. the version you were trained on) to get the precise delta: added, removed, renamed, changed. Also returns the version's declared engines (Node/runtime floor). Large surfaces are paged, 80 symbols per call: totalSymbols is the size, query filters by name, offset pages. shallow: true means the API lives on an interface's members that are not listed, and the note says where to read them. For framework file/convention changes (not exported symbols), consult the official migration guide / Context7 instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoPart of a symbol name (case-insensitive); returns only matching symbols
offsetNoIndex of the first symbol to return, to page past the first 80
packageYesnpm package name
versionNoTarget version (defaults to latest)
knownVersionNoA version you already know; returns the API delta from it to the target

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Index of the first symbol to return, to page past the first 80",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Part of a symbol name (case-insensitive); returns only matching symbols",
+  "maxLength": 100,
+  "type": "string"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say read-only and open-world; the description adds substantial behavior beyond that — the data is version-exact and absent from training data, the return includes declared engines (runtime floor), surfaces are paged at 80 symbols per call, and `shallow: true` signals API hiding on interface members with a pointer to where they live. This is exactly the kind of operational context annotations cannot carry.

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?

Front-loaded with the core value ('A package version's TYPED API ... exact to the version') then progressively adds routing, delta, paging, and escalation guidance. Dense but each clause carries information; the routing and paging sentences could be tightened slightly.

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 no output schema, the description still names the response fields an agent needs (totalSymbols, query, offset, shallow) and explains the delta semantics and engines output. Nothing required to call it correctly or interpret the result is missing.

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

Parameters4/5

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

Schema coverage is 100% so the baseline is 3, but the description adds real meaning: knownVersion yields a precise delta classified as added/removed/renamed/changed, query filters by symbol name, offset pages past the first 80, and totalSymbols reports full size. It stops short of explaining the default of version beyond the schema's note.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: the TYPED API (exported symbols and signatures) of a package version, sourced from shipped .d.ts or DefinitelyTyped. The title reinforces it and the description explicitly distinguishes itself from the sibling resolve_surface (runtime existence) and verify (install safety).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Use before writing code against a package whose API may have moved') and routes the agent to named alternatives with the exact condition selecting each: resolve_surface for runtime/import behavior, verify for install safety, migration guides/Context7 for framework conventions.

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

All lurq toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources