Skip to main content

CodePic

by io.github.abelce

Overview Discussions Admin

List Templates

list_templates

List all available CodePic diagram templates. Use this ONLY when the user has explicitly asked to browse, list, or pick from templates (e.g. "show me templates", "列出模板"). Do NOT call this as a preparatory step when the user just described a diagram they want — in that case go straight to create_diagram. Discovering slugs here is only meaningful before a user-confirmed create_from_template call.

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

Input Schema

Name	Required	Description	Default
`category`	No	Filter by category

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 27, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "design",
-  "flowchart",
-  "collaboration",
-  "engineering"
-]New value: +[
+  "collaboration",
+  "planning",
+  "design",
+  "flowchart",
+  "engineering"
+]

Changed1 schema field changedSep 11, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "design",
-  "planning",
-  "flowchart",
-  "collaboration",
-  "engineering"
-]New value: +[
+  "planning",
+  "design",
+  "flowchart",
+  "collaboration",
+  "engineering"
+]

Changed1 schema field changedSep 11, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "flowchart",
-  "collaboration",
-  "design",
-  "engineering"
-]New value: +[
+  "design",
+  "planning",
+  "flowchart",
+  "collaboration",
+  "engineering"
+]

Changed1 schema field changedAug 22, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "collaboration",
-  "flowchart",
-  "planning",
-  "design",
-  "engineering"
-]New value: +[
+  "planning",
+  "flowchart",
+  "collaboration",
+  "design",
+  "engineering"
+]

Changed1 schema field changedAug 18, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "flowchart",
-  "collaboration",
-  "planning",
-  "design",
-  "engineering"
-]New value: +[
+  "collaboration",
+  "flowchart",
+  "planning",
+  "design",
+  "engineering"
+]

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "flowchart",
-  "planning",
-  "design",
-  "engineering",
-  "collaboration"
-]New value: +[
+  "flowchart",
+  "collaboration",
+  "planning",
+  "design",
+  "engineering"
+]

Changed1 schema field changedAug 13, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "flowchart",
-  "design",
-  "engineering",
-  "collaboration"
-]New value: +[
+  "flowchart",
+  "planning",
+  "design",
+  "engineering",
+  "collaboration"
+]

Changed1 schema field changedAug 9, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "design",
-  "engineering",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "flowchart",
+  "design",
+  "engineering",
+  "collaboration"
+]

Changed1 schema field changedAug 8, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "design",
-  "planning",
-  "engineering",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "design",
+  "engineering",
+  "collaboration",
+  "flowchart"
+]

Changed1 schema field changedAug 2, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "engineering",
-  "design",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "design",
+  "planning",
+  "engineering",
+  "collaboration",
+  "flowchart"
+]

Changed1 schema field changedJul 25, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "engineering",
-  "planning",
-  "design",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "engineering",
+  "design",
+  "collaboration",
+  "flowchart"
+]

Changed1 schema field changedJul 19, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "design",
-  "collaboration",
-  "engineering",
-  "flowchart"
-]New value: +[
+  "engineering",
+  "planning",
+  "design",
+  "collaboration",
+  "flowchart"
+]

Changed1 schema field changedJul 14, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "design",
-  "planning",
-  "collaboration",
-  "engineering",
-  "flowchart"
-]New value: +[
+  "planning",
+  "design",
+  "collaboration",
+  "engineering",
+  "flowchart"
+]

Changed1 schema field changedJul 13, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "collaboration",
-  "engineering",
-  "flowchart",
-  "design"
-]New value: +[
+  "design",
+  "planning",
+  "collaboration",
+  "engineering",
+  "flowchart"
+]

Changed1 schema field changedJul 9, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "collaboration",
-  "planning",
-  "engineering",
-  "flowchart",
-  "design"
-]New value: +[
+  "planning",
+  "collaboration",
+  "engineering",
+  "flowchart",
+  "design"
+]

Changed1 schema field changedJul 8, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "engineering",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "collaboration",
+  "planning",
+  "engineering",
+  "flowchart",
+  "design"
+]

Changed1 schema field changedJul 7, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "engineering",
-  "planning",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "planning",
+  "engineering",
+  "flowchart",
+  "collaboration",
+  "design"
+]

Changed1 schema field changedJul 4, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "planning",
-  "engineering",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "engineering",
+  "planning",
+  "flowchart",
+  "collaboration",
+  "design"
+]

Changed1 schema field changedJun 23, 2026

changedInput schema / properties / category / enum

Previous value: -[
-  "engineering",
-  "flowchart",
-  "planning",
-  "collaboration",
-  "design"
-]New value: +[
+  "planning",
+  "engineering",
+  "flowchart",
+  "collaboration",
+  "design"
+]

First observedJun 17, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden; it signals a read-only enumeration by phrasing and adds non-obvious behavioral context — that the discovered slugs are only actionable ahead of a user-confirmed `create_from_template` call. It omits return volume/shape (how many templates, what fields come back), which for a no-annotation tool would have been useful.

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?

Three front-loaded sentences: what it does, when to use it, when not to. Every clause earns its place, including the guardrail against using it as a discovery step mid-task.

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?

Complete for a zero-required-param browse tool with no output schema: intent, routing, and the downstream dependency on `create_from_template` are all covered. What is missing is any hint of the returned fields (slug/name/description) or result set size, which an agent would want before formatting a response.

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% and the single optional enum for `category` is fully documented in the schema, so the baseline of 3 applies. The description's 'List all available' actually implies no filtering and never mentions the category parameter, adding nothing beyond the schema.

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 all available CodePic diagram templates') and immediately distinguishes itself from siblings by naming `create_diagram` and `create_from_template` as the correct destinations for adjacent intents.

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?

Gives an explicit when ('user has explicitly asked to browse, list, or pick'), an explicit when-not ('Do NOT call this as a preparatory step when the user just described a diagram'), and names the alternative tool to use instead. The trigger examples in English and Chinese further reduce ambiguity.

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

All CodePic tools Inspect

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