Skip to main content
Glama

inspect_manifest

Inspect an MCP server's declared tools, resources, and prompts without executing actions, and detect manifest rug-pulls by comparing against prior recorded runs.

Instructions

Inspect an MCP server's declared capabilities (tools, resources, prompts) without executing tool actions or tracing syscalls. Also checks for manifest rug-pulls against prior recorded runs.

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

Input Schema

NameRequiredDescriptionDefault
commandYes
timeoutNo
transportNostdio

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description does useful work: it discloses non-invasiveness (no tool execution, no syscall tracing) and statefulness implied by comparing against 'prior recorded runs'. The significant undisclosed behavior is that it takes a 'command' - presumably spawning the target MCP server process - which is a real side effect an agent should know about, along with any network or sandbox implications.

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?

Two compact sentences, both load-bearing: the first defines the scope and its non-invasive boundary, the second adds the rug-pull capability. Nothing is repeated from the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is fairly waived, but for a three-parameter tool with 0% schema coverage and no annotations the description leaves too much open: how 'command' is executed, what 'transport' values do, and what 'prior recorded runs' means in terms of stored state. It is evocative but not sufficient to call the tool confidently.

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% across three parameters, so the description must carry the semantics and it largely does not. At best, 'Inspect an MCP server's capabilities' lets an agent guess that 'command' launches the server; 'timeout' and 'transport' (default 'stdio') are given no meaning, and the array-vs-string form of 'command' is never clarified.

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?

Names a specific verb and resource ('Inspect an MCP server's declared capabilities (tools, resources, prompts)') and adds a second, distinct function ('checks for manifest rug-pulls against prior recorded runs'). It implicitly separates itself from an execution/tracing-based tool ('without executing tool actions or tracing syscalls') rather than naming audit_server outright, which keeps it just 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?

The phrase 'without executing tool actions or tracing syscalls' implies the static-inspection use case versus a runtime audit, so an agent can infer the choice. However, there is no explicit when-to-use statement, no prerequisites (e.g., whether the server must be installed or reachable), and the sibling is never named as the alternative.

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