Skip to main content
Glama
Sign In
@lpm-registry/mcp-server

@lpm-registry/mcp-server

Official
by lpm-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

lpm_package_info

Retrieve comprehensive metadata for an LPM package, including versions, description, download stats, AI analysis, compatibility, and readme.

Instructions

Get metadata for an LPM package including versions, description, downloads, AI analysis, compatibility, and readme

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

Input Schema

NameRequiredDescriptionDefault
nameYesPackage name in owner.package-name or @lpm.dev/owner.package-name format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states 'Get metadata' implying a read-only operation, but does not disclose any additional behaviors such as response size, rate limits, or authentication requirements. Adequate but minimal.

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?

The description is a single sentence that efficiently conveys all necessary information without redundancy. Every part is meaningful.

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?

Given the tool has only one parameter and no output schema, the description adequately explains what the tool returns (a list of metadata items), making it complete for a simple lookup tool.

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 100% (the single parameter 'name' has a clear description in the schema). The tool description does not add any extra meaning beyond what the schema already provides, earning the baseline score of 3.

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?

The description clearly states the verb 'Get' and resource 'metadata for an LPM package', listing specific items (versions, description, downloads, AI analysis, compatibility, readme). This differentiates it from siblings like lpm_package_context or lpm_quality_report.

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?

While the purpose is clear, there is no explicit guidance on when to use this tool versus alternatives. No 'when not to use' or mention of other tools for specific needs.

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

Deploy Server

Other Tools