Skip to main content
Glama

List analysis providers

vestige_list_providers
Read-only

Lists available analysis providers with their capabilities and live availability, plus installation guidance when a required tool such as Ghidra is missing.

Instructions

List providers with capabilities and live availability (including installation guidance when a tool like Ghidra is missing).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vestige_list_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value beyond that by disclosing that availability is probed live and that the response can include remediation content (installation guidance for missing tools), which helps an agent decide to call it when diagnosing a gap.

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?

A single sentence, front-loaded with the core action ('List providers') and followed by qualifying detail in a compact parenthetical. Nothing is wasted, though the parenthetical phrasing is slightly denser than necessary.

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?

For a zero-parameter, read-only listing tool with no output schema, the description supplies the essential information about what comes back: capabilities, live availability, and installation guidance. A brief note on cost or latency of the live availability probe would make it fully complete.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the schema already declares an empty object with additionalProperties=false. Baseline 4 applies since the description cannot and need not add parameter detail.

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?

States a specific verb and resource ('List providers') and enriches it with what the listing contains: capabilities, live availability, and installation guidance. It is clearly distinct from every sibling (which act on targets, jobs, findings, evidence, reports), though it does not explicitly contrast itself with any of them.

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?

Usage is implied rather than stated: the mention of 'live availability' and 'installation guidance when a tool like Ghidra is missing' suggests calling this before analysis or when a dependency appears absent. There is no explicit when-to-use, when-not-to-use, or named alternative.

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