Skip to main content
Glama

Look up recorded facts about an MCP server

get_lowdown
Read-onlyIdempotent

Lowdown(로우다운) looks 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 a package ('npm:@scope/name', 'pypi:name'). Returns dated facts, not scores: status (latest daily initialize/tools/list check: answered, required authentication, or no response), registry (what the official MCP Registry declares, and changes in the last 30 days), packages (declared npm/PyPI packages: deprecated, yanked, archived, or 404), scanner (tool definition changes and content markers such as a new URL or invisible characters), payment (HTTP 402 terms on the latest check: x402, MPP or L402; payment support declared in the server card or ERC-8004 file; Lowdown does not pay), and agent reports. Optional menu returns one part, e.g. 'install-check' or 'payment'. Absence of data says nothing about a server. Each answer ends with a source block (dataset, CC BY 4.0, retrieval time).

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

Input Schema

NameRequiredDescriptionDefault
menuNoOptional. Before installing, use 'install-check' (status, payment, packages, declared-vs-observed, content-flags). 'change-watch' = what changed recently, or one part: status, payment, packages, tools, declared-vs-observed, content-flags, tool-list, registry, history, agent-reports. Omit or 'full' for everything.
targetYesMCP Registry name with the mcp: prefix (e.g. 'mcp:io.github.user/server'), a short name, or a package with the npm: or pypi: prefix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / menu / description
      Previous value: -"Optional. Before installing, use 'install-check' (status, packages, declared-vs-observed, content-flags). 'change-watch' = what changed recently, or one part: status, packages, tools, declared-vs-observed, content-flags, tool-list, registry, history, agent-reports. Omit or 'full' for everything."New value: +"Optional. Before installing, use 'install-check' (status, payment, packages, declared-vs-observed, content-flags). 'change-watch' = what changed recently, or one part: status, payment, packages, tools, declared-vs-observed, content-flags, tool-list, registry, history, agent-reports. Omit or 'full' for everything."
  2. Changed1 schema field changed
    • changedInput schema / properties / menu / enum
      Previous value: -[
      -  "install-check",
      -  "change-watch",
      -  "full",
      -  "status",
      -  "packages",
      -  "tools",
      -  "declared-vs-observed",
      -  "content-flags",
      -  "tool-list",
      -  "registry",
      -  "history",
      -  "agent-reports"
      -]New value: +[
      +  "install-check",
      +  "change-watch",
      +  "full",
      +  "status",
      +  "payment",
      +  "packages",
      +  "tools",
      +  "declared-vs-observed",
      +  "content-flags",
      +  "tool-list",
      +  "registry",
      +  "history",
      +  "agent-reports"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / menu / description
      Previous value: -"Optional. 'install-check' (before installing: status, packages, declared-vs-observed, content-flags), 'change-watch' (what changed recently), or one part: status, packages, tools, declared-vs-observed, content-flags, tool-list, registry, history, agent-reports. Omit or 'full' for everything."New value: +"Optional. Before installing, use 'install-check' (status, packages, declared-vs-observed, content-flags). 'change-watch' = what changed recently, or one part: status, packages, tools, declared-vs-observed, content-flags, tool-list, registry, history, agent-reports. Omit or 'full' for everything."
  4. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real behavior beyond that: results are dated facts rather than scores, missing data is not evidence, Lowdown never pays, and every answer carries a CC BY 4.0 source block. That nudges it above baseline but it is not a full behavioral disclosure.

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?

Purpose is front-loaded, then the return shape, then the optional parameter. The long enumeration of facts is dense but each named part maps to a menu option or output section, so it earns its space; a slightly tighter grouping would make it easier to scan.

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?

No output schema exists, so the description carries the burden of explaining return values — and it does, naming each facts section (status, registry, packages, scanner, payment, agent reports) plus the source block. For a two-parameter lookup tool, an agent has everything needed to call it and read the result.

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 enum for `menu` is already documented in the schema, so the description's restatement ("returns one part, e.g. 'install-check' or 'payment'") adds little. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

Specific verb ("looks up recorded facts") plus resource (an MCP server) with a stated moment of use ("before installing or connecting"). It also names the accepted identifier forms, so the agent knows exactly what class of thing this tool operates on.

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 a clear context: use before installing or connecting, and the description plus the menu schema point to 'install-check' for pre-install vetting. It doesn't explicitly contrast with the sibling find_servers (discovery vs. verification), so there is no explicit when-not guidance.

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