Skip to main content
Glama
ngpvan-mcp

ngpvan-mcp

by Emmanuel-m42

list_folders

Read-onlyIdempotent

Retrieve the saved-list folders visible to the current API key, so you can identify folder IDs and organize or locate lists within an organization's VAN data.

Instructions

The saved-list folders this API key can see.

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_folders"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, closed-world, and non-destructive behavior. The description adds the useful access-scoping detail that results are limited to folders visible to the API key, but it does not mention pagination, ordering, empty results, or other behavioral traits beyond the schema.

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 definition is a single sentence fragment with no wasted wording, and it front-loads the resource and access scope. It could be slightly stronger if it used an explicit action verb, but it remains easy to parse.

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

Completeness3/5

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

For a simple zero-parameter read-only list tool with annotations and an output schema, the description covers the core resource and visibility scope. However, it omits usage context and does not clarify what 'saved-list folders' relates to in the broader API, leaving some selection ambiguity.

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?

This tool has zero parameters, so there is no parameter semantics for the description to clarify. The baseline score of 4 is appropriate given that the empty input schema accurately reflects the tool's signature.

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 identifies a specific resource, 'saved-list folders,' and narrows scope to those visible to the API key. It is clear what is being returned, though it relies on the tool name to supply the listing action and does not differentiate from any sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to call this tool versus other list or lookup operations, and no stated exclusions or prerequisites. The agent is left to infer usage from the resource name alone.

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