Skip to main content
Glama
Sign In
mcp-server-wrapper

mcp-server-wrapper

by veithly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mcp_list_tools

Discover available tools across MCP servers. Specify a server to see its tools, or view all tools from connected servers.

Instructions

List available tools from MCP servers. If server is specified, connects to that server and lists its tools. Otherwise lists tools from all connected servers.

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": "mcp_list_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNoServer ID to list tools from
patternNoFilter tools by name pattern

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 convey behavioral traits. It mentions connection and listing but lacks details on side effects, permissions, error handling, or caching behavior.

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 concise sentences with no wasted words, effectively communicating core functionality.

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?

Given the low complexity and full schema coverage, the description is nearly complete. It could mention the return format (list of tools with names/descriptions) since no output schema is provided.

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 coverage is 100% with both parameters described. The description adds no extra meaning beyond the schema, so baseline 3 is appropriate.

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 tool lists available tools from MCP servers and specifies conditional behavior based on the server parameter. It distinguishes from sibling tools like mcp_add_server, mcp_invoke, etc., which have different purposes.

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 description implies usage by describing conditional behavior but does not explicitly state when to use versus alternatives, nor does it provide exclusions or guidance on when not to use.

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