Denser

List knowledge sources

list_sources

Read-onlyIdempotent

List a chatbot's knowledge sources (websites, files, Q&A, text) with their indexing status. Pass dataSourceId to list one website source's pages instead.

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

Input Schema

Name	Required	Description
`page`	No	With dataSourceId: the page of results, from 1.
`pageSize`	No	With dataSourceId: pages per result page (default 50).
`chatbotId`	No	The chatbot ID from list_chatbots. Omit it to use the chatbot this session is about.
`dataSourceId`	No	A website source's ID, to list its pages.
`nameContains`	No	Only sources whose name contains this, or with dataSourceId, pages whose URL does; ignores case.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds context the annotations don't: results include per-source indexing status, and the tool has a dual-mode behavior where the same call shape returns pages rather than sources. It doesn't discuss pagination or result limits for the top-level listing, which is a minor gap.

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 sentences, zero waste. The primary behavior is front-loaded and the secondary mode follows immediately, which matches how an agent would read it.

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?

With five all-optional parameters, no output schema, and 100% schema coverage, the description carries the return-value burden well by naming indexing status as a result field. The one omission is pagination: page/pageSize are scoped "With dataSourceId" in the schema, and the description never clarifies how the top-level source list is bounded or paged.

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 100%, so every parameter (page, pageSize, chatbotId, dataSourceId, nameContains) is already documented, including defaults and the session-chatbot fallback. The description reinforces the dataSourceId mode switch but adds no syntax, format, or edge-case detail beyond the schema — 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?

States a specific verb and resource ("List a chatbot's knowledge sources") and enumerates the source types (websites, files, Q&A, text) plus the returned attribute (indexing status). It also discloses the second mode — passing dataSourceId lists a single website source's pages — so an agent knows exactly what the tool covers without opening the schema.

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

Usage Guidelines4/5

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

The second sentence gives an explicit branch condition: pass dataSourceId to list one website source's pages "instead" of the source list. That is genuine when-to-use guidance for the tool's two modes. It stops short of routing the agent away from siblings such as get_source_status or search_knowledge_base, which is the only missing piece.

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

All Denser tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?