Skip to main content
Glama

CodePic

by io.github.abelce
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "design",
-  "planning",
-  "flowchart",
-  "collaboration",
-  "engineering"
-]New value: +[
+  "planning",
+  "design",
+  "flowchart",
+  "collaboration",
+  "engineering"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "flowchart",
-  "collaboration",
-  "design",
-  "engineering"
-]New value: +[
+  "design",
+  "planning",
+  "flowchart",
+  "collaboration",
+  "engineering"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "collaboration",
-  "flowchart",
-  "planning",
-  "design",
-  "engineering"
-]New value: +[
+  "planning",
+  "flowchart",
+  "collaboration",
+  "design",
+  "engineering"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "flowchart",
-  "collaboration",
-  "planning",
-  "design",
-  "engineering"
-]New value: +[
+  "collaboration",
+  "flowchart",
+  "planning",
+  "design",
+  "engineering"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "flowchart",
-  "planning",
-  "design",
-  "engineering",
-  "collaboration"
-]New value: +[
+  "flowchart",
+  "collaboration",
+  "planning",
+  "design",
+  "engineering"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "flowchart",
-  "design",
-  "engineering",
-  "collaboration"
-]New value: +[
+  "flowchart",
+  "planning",
+  "design",
+  "engineering",
+  "collaboration"
+]
  7. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "design",
-  "engineering",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "flowchart",
+  "design",
+  "engineering",
+  "collaboration"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "design",
-  "planning",
-  "engineering",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "design",
+  "engineering",
+  "collaboration",
+  "flowchart"
+]
  9. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "engineering",
-  "design",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "design",
+  "planning",
+  "engineering",
+  "collaboration",
+  "flowchart"
+]
  10. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "engineering",
-  "planning",
-  "design",
-  "collaboration",
-  "flowchart"
-]New value: +[
+  "planning",
+  "engineering",
+  "design",
+  "collaboration",
+  "flowchart"
+]
  11. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "design",
-  "collaboration",
-  "engineering",
-  "flowchart"
-]New value: +[
+  "engineering",
+  "planning",
+  "design",
+  "collaboration",
+  "flowchart"
+]
  12. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "design",
-  "planning",
-  "collaboration",
-  "engineering",
-  "flowchart"
-]New value: +[
+  "planning",
+  "design",
+  "collaboration",
+  "engineering",
+  "flowchart"
+]
  13. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "collaboration",
-  "engineering",
-  "flowchart",
-  "design"
-]New value: +[
+  "design",
+  "planning",
+  "collaboration",
+  "engineering",
+  "flowchart"
+]
  14. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "collaboration",
-  "planning",
-  "engineering",
-  "flowchart",
-  "design"
-]New value: +[
+  "planning",
+  "collaboration",
+  "engineering",
+  "flowchart",
+  "design"
+]
  15. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "engineering",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "collaboration",
+  "planning",
+  "engineering",
+  "flowchart",
+  "design"
+]
  16. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "engineering",
-  "planning",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "planning",
+  "engineering",
+  "flowchart",
+  "collaboration",
+  "design"
+]
  17. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "planning",
-  "engineering",
-  "flowchart",
-  "collaboration",
-  "design"
-]New value: +[
+  "engineering",
+  "planning",
+  "flowchart",
+  "collaboration",
+  "design"
+]
  18. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "engineering",
-  "flowchart",
-  "planning",
-  "collaboration",
-  "design"
-]New value: +[
+  "planning",
+  "engineering",
+  "flowchart",
+  "collaboration",
+  "design"
+]
  19. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses the slug-discovery intent and the 'only meaningful before a user-confirmed create_from_template' constraint, but says nothing about return format, pagination, or whether the list is filtered by the category param.

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?

Front-loads the core action, then the usage constraints, in three tight sentences with the critical exclusion in the middle. The parenthetical bilingual example is slightly extraneous but aids intent matching.

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?

No output schema exists, but the description hints at the meaningful return content (discoverable slugs usable with create_from_template), which is the key info for a list tool. Minor gap in not describing pagination or result shape.

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 category enum is fully documented in the schema, so baseline 3 applies. The description adds no meaning about the category filter beyond what the schema already provides.

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 explicitly distinguishes itself from two siblings by naming create_diagram and create_from_template. An agent can tell exactly what this tool is and is not for.

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 explicit when-to-use ('ONLY when the user has explicitly asked to browse, list, or pick') and when-not ('Do NOT call this as a preparatory step'), and names the alternative (create_diagram) for the excluded case. The routing logic is unambiguous.

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

All CodePic 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