Skip to main content
Glama
Sign In
lowdown-proxy

lowdown-proxy

by PetShopBros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_lowdown

Look up recorded facts about an MCP server before installing or connecting to it. Accepts an MCP Registry name ('mcp:io.github.user/server'), a short name, or an npm package ('npm:@scope/name').

Instructions

Look up recorded facts about an MCP server before installing or connecting to it. Accepts an MCP Registry name ('mcp:io.github.user/server'), a short name, or an npm package ('npm:@scope/name'). Returns, in order: registry (what the official MCP Registry declares, and changes in the last 30 days); packages (for each declared npm package: npm's latest version, whether that latest version is marked deprecated, and whether npm answers 404, checked daily); scanner (daily initialize and tools/list observations over 30 days, including when tool definitions last changed); and interactions reported by agents. When a declared npm package is deprecated or answers 404, the first sentence of message says so. These are recorded facts with dates and sources, not scores. Absence of data says nothing about a server's status.

Input Schema

NameRequiredDescriptionDefault
targetYesMCP Registry name with the mcp: prefix (e.g. 'mcp:io.github.user/server'), a short name, an npm package with the npm: prefix (e.g. 'npm:@scope/name'), or an id such as 'agent:some-agent-id'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.17
    • changedInput schema / properties / target / description
      Previous value: -"MCP Registry name with the mcp: prefix (e.g. 'mcp:io.github.user/server'), a short name, or an id such as 'agent:some-agent-id'"New value: +"MCP Registry name with the mcp: prefix (e.g. 'mcp:io.github.user/server'), a short name, an npm package with the npm: prefix (e.g. 'npm:@scope/name'), or an id such as 'agent:some-agent-id'"
  2. Changed1 schema field changedv0.1.15
    • changedInput schema / properties / target / description
      Previous value: -"Identifier of the agent/tool/service. e.g. 'mcp:vendor/tool-name' or 'agent:some-agent-id'"New value: +"MCP Registry name with the mcp: prefix (e.g. 'mcp:io.github.user/server'), a short name, or an id such as 'agent:some-agent-id'"
  3. First observedv0.1.11

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does substantial work: it enumerates the four returned sections in order, states the data is recorded daily/over 30 days, notes what happens when a package is deprecated or 404s, and warns that absence of data is not a negative signal. Gaps remain around auth/pricing or error behavior for an unrecognized target, but the disclosure is well above typical.

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-loads purpose in the first sentence, then accepted inputs, then return structure — a sensible order with no filler. The return-section enumeration is wordy but earns its place since there is no output schema.

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?

With no output schema and no annotations, the description must explain what comes back and how fresh it is, and it does so section by section with the 30-day/daily cadence. It stops short of describing behavior on an unresolvable target or any failure modes, which is the main remaining hole.

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% and the single `target` parameter is already documented with the same accepted formats in the schema. The description's restatement of registry/npm formats adds no syntax or validation detail beyond that, so baseline 3 applies.

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 and resource ("Look up recorded facts about an MCP server") plus the calling context (before installing or connecting). This is clearly distinct from the sibling tools compare_tools, get_node_stats and record_interaction, so an agent can route without opening any schema.

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

Usage Guidelines4/5

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

Gives an explicit trigger — call this before installing or connecting to a server — which is real when-to-use guidance. It does not name alternatives or state when not to use it, but the sibling names make the boundary obvious.

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