CueFrame

List Templates

list_templates

Read-onlyIdempotent

List this organization's saved templates. Follow pagination.nextCursor with after to read further pages. Public catalog slugs are not enumerated here; read a known public slug with get_template.

Input Schema

Name	Required	Description	Default
`after`	No	Opaque cursor from the previous page's `pagination.nextCursor`. Forward-only.
`limit`	No	Page size (1..100), default 20. Out-of-range or unparseable clamps into the range.

Output Schema

Name	Required	Description	Default
`data`	No
`pagination`	No	Cursor pagination metadata.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maximum": 100,
+    "minimum": 1,
+    "type": "integer"
+  }
+}
```
- addedInput schema / properties / limit / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / limit / maximum
```
Removed value: -100
```
- removedInput schema / properties / limit / minimum
```
Removed value: -1
```
- removedInput schema / properties / limit / type
```
Removed value: -"integer"
```
AddedOct 18, 2026

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 and closed-world, so safety is covered. The description adds behavior beyond that: how to continue pagination (follow pagination.nextCursor into after) and that public catalog entries are excluded from results — both are non-obvious result-set facts.

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 short sentences, each doing distinct work: scope, pagination, exclusion plus redirect. Scope is front-loaded and there is no redundant restatement of the 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?

With a full schema, an output schema, and complete annotations, the description covers the remaining gaps an agent needs: scope, paging continuation, and what is not returned. Minor omissions like ordering or empty-result behavior are tolerable given the output schema.

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% with both params fully documented, so the baseline is 3. The description goes further by linking the response field pagination.nextCursor to the `after` parameter, clarifying the cursor chaining contract that the schema alone states only abstractly.

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 this organization's saved templates') with an explicit scope qualifier that separates it from catalog-wide listing tools. An agent can immediately tell this returns org-owned templates, not the public catalog.

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?

Explicitly excludes public catalog slugs and routes the agent to get_template for reading a known public slug, which is real when-not guidance with a named alternative. It stops short of naming list_catalog as the tool to browse the public catalog, so the alternative routing is only partial.

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

All CueFrame 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.