Skip to main content
Glama
Sign In

Denser

by ai.denser
OverviewDiscussionsAdmin

List chatbots

list_chatbots
Read-onlyIdempotent

List the Denser chatbots in the connected workspace with their IDs, status, channels and source counts. Call this first when you don't know a chatbot's ID; every other tool takes chatbotId.

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

Input Schema

NameRequiredDescriptionDefault
nameContainsNoOnly chatbots whose title contains this, ignoring case.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds value beyond that by naming what comes back (IDs, status, channels, source counts) in the absence of an output schema. It doesn't mention pagination or result limits, which keeps it from a 5.

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, front-loaded with the action and result contents, then the usage rule. No filler and nothing restated from structured fields.

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?

For a read-only discovery tool with rich annotations, the description covers purpose, return shape, and call-ordering guidance. The only gap is not mentioning that results can be narrowed with nameContains, which an agent might otherwise miss.

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?

There is only one optional parameter and the schema documents it fully at 100% coverage ('nameContains' with case-insensitive contains semantics). The description adds nothing about the filter, so baseline 3 is correct.

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 the Denser chatbots in the connected workspace'), and enumerates the returned fields (IDs, status, channels, source counts). The closing sentence distinguishes it from every sibling by noting all other tools take chatbotId.

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

Usage Guidelines5/5

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

Explicitly prescribes when to use it: 'Call this first when you don't know a chatbot's ID; every other tool takes chatbotId.' This gives both the trigger condition and the relationship to the alternatives.

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

All Denser toolsInspect
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