Skip to main content
Glama

list_documents

Lists files and folders in a course's Documents area; provide a folder path to view its contents.

Instructions

Files and folders in a course's Documents area. Pass a folder's path to list inside it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "course": "<course>"
    },
    "name": "list_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo/
courseYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, but 'list' plus 'files and folders' makes the read-only nature inferable. It adds one useful behavioral detail, that `path` scopes the listing to inside a folder, yet says nothing about pagination, permissions, recursion depth, or whether the default '/' returns the course root.

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?

Two short sentences with no filler, and the scope statement comes first. The opening is a sentence fragment with no verb, which slightly weakens front-loading but costs no clarity.

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?

This is a simple two-parameter read tool with an output schema, so the bar is modest, and the description covers purpose and path semantics. It still leaves the required `course` parameter and the default path behavior unexplained, which an agent must guess at before calling.

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 description coverage is 0% with two parameters, so the description must compensate. It explains `path` as the folder to list inside, but leaves the default '/' unstated and gives no meaning for the required `course` parameter beyond the passing phrase 'a course's Documents area'.

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 the specific resource and scope: files and folders in a course's Documents area, which lets an agent distinguish this listing operation from siblings like download_document. It never explicitly contrasts with a sibling or states the verb 'list' outright, relying on the tool name for that, so it stops short of a 5.

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?

It gives one concrete usage instruction: pass a folder's `path` to list inside it, which implies browsing a course's document tree. There is no when-to-use versus when-not guidance, no mention of the default root listing behavior, and no routing to alternatives such as download_document for retrieving content.

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