Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

List the client’s roots

list_roots
Read-only

List the folders a client exposes to this server, verify whether each path exists, and count roots/list_changed notifications received.

Instructions

Send a roots/list request and report the folders (file:// roots) the client exposes to this server, whether each path exists on the machine running the server, and how many notifications/roots/list_changed the client has sent. Reads nothing inside the folders.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true. The description adds real behavioral context beyond that: the tool issues an outbound protocol request to the client, performs a local existence check on each returned path, and counts list_changed notifications, which tells the agent the response has three distinct components. The explicit 'reads nothing inside the folders' clause rules out an assumption an agent could easily make. It stops short of noting that the call depends on client availability or that notification counts are cumulative, hence a 4.

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?

One sentence, front-loaded with the action, followed by the three reported values in the order an agent would care about them, and closed with a scope exclusion. No redundant or filler phrasing.

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?

There is no output schema, so the description carries the return-value burden and does so by naming all three response components (roots, path existence, notification count). For a zero-parameter read-only tool, nothing an agent needs in order to call it correctly is missing.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not waste words restating an empty schema.

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?

The description names a specific protocol operation (roots/list) and enumerates exactly what is reported: the exposed file:// roots, whether each path exists on the server machine, and the count of roots/list_changed notifications. That is a concrete verb-plus-resource statement. It does not explicitly contrast with siblings such as inspect_client or list_seen_clients, but the scope is unambiguous on its own.

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: an agent infers it should call this to discover the client's exposed roots. The closing clause 'Reads nothing inside the folders' functions as a soft boundary, telling the agent not to use it to inspect folder contents. 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.