MCP Test MCP

Overview Schema Source Related Servers Discussions Admin

List Resources

list_resources

Retrieve a comprehensive list of all resources on the connected MCP server, including URIs, names, descriptions, and MIME types, with metadata for reliable access.

Instructions

List all resources available on the connected MCP server.

Retrieves comprehensive information about all resources exposed by the target server, including URIs, names, descriptions, and MIME types to enable accurate resource access.

Returns: Dictionary with resource listing including: - success: True on successful retrieval - resources: List of resource objects with uri, name, description, mimeType - metadata: Total count, server info, timing information

Raises: Returns error dict if not connected or retrieval fails

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.2Sep 8, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
First observedDec 7, 2025

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the return format (success, resources, metadata), includes error behavior ('RETURNS error dict if not connected or retrieval fails'), and implies a read-only operation. This is transparent enough for a listing tool.

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?

The description is fairly concise and well-structured with sections for action, return, and errors. However, there is minor redundancy between 'List all resources' and 'Retrieves comprehensive information about all resources...', which slightly detracts from precision.

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?

The description covers the essential context: what it does, what it returns (including a success flag and metadata), and error conditions. It lacks mention of pagination or limits, but for a resource-listing operation on an MCP server, this is reasonably complete given there is no formal output schema.

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?

The input schema is empty (0 parameters), so schema description coverage is 100% vacuously. The baseline of 3 applies; the description adds no parameter-specific details because there are none.

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 states a specific verb ('List') and resource ('all resources available on the connected MCP server'), and distinguishes it from sibling tools like list_tools and list_prompts by focusing solely on resources. It also details what information is returned (URIs, names, descriptions, MIME types).

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 clearly explains what the tool does but does not explicitly state when to use it over alternatives (e.g., list_tools, read_resource). It implies its purpose but lacks direct comparative guidance.

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

Deploy Server