Skip to main content
Glama
Sign In
ragflow-kb-mcp

ragflow-kb-mcp

by feci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

ragflow_list_agent_templates

Read-only

Lists built-in agent templates, or returns one template's DSL when given a template_id, to supply the configuration needed for creating an agent.

Instructions

List the built-in agent templates; pass template_id to get one template's DSL for ragflow_create_agent.

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

Input Schema

NameRequiredDescriptionDefault
template_idNoReturn this template including its DSL

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the read-only, closed-world safety profile is covered without the description. The description adds that these are built-in (static, server-provided) templates, which is mild context, but says nothing about result counts, pagination, or what a template record contains beyond DSL.

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?

A single compact sentence covering both modes, with the primary list action front-loaded and the optional parameter path following the semicolon. Nothing is redundant with the tool name or schema.

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?

An output schema exists so return values need no explanation, annotations cover safety, and there is only one optional parameter whose two behaviors are both described. The definition is essentially sufficient, with only minor omissions around result set size or ordering.

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?

Schema coverage is 100% and the schema already documents template_id as "Return this template including its DSL," so the baseline is 3. The description earns an extra point by adding purpose the schema lacks: that the returned DSL is intended as input to ragflow_create_agent, making the parameter's downstream value clear.

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 built-in agent templates") and distinguishes the two modes of operation: bulk list, or single template DSL via template_id. It also disambiguates from ragflow_list_agents by scoping to built-in templates and names the downstream consumer, ragflow_create_agent.

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?

Makes the follow-on workflow explicit: pass template_id to retrieve a template's DSL for ragflow_create_agent, so an agent knows why it would use the parameterized form. It does not state when not to use this tool (e.g. versus ragflow_list_agents for existing custom agents), so it stops short of full alternative routing.

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

Deploy Server

Other Tools