Skip to main content
Glama
Sign In

CheckFlow

by io.checkflow
OverviewDiscussionsAdmin

List template permissions

list_template_permissions
Read-onlyIdempotent

Who can see and run the checklists made from a template. These are about the checklists rather than about the template: none of them lets anybody edit the template, which is a team role rather than a permission. An empty list is a real answer and means only administrators see this template's checklists -- it is not the same as a template that does not exist, which refuses. Read this before set_template_permissions, which replaces the whole set.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "templateKey": "<templateKey>"
    },
    "name": "list_template_permissions"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateKeyYesThe template's key, from list_templates. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description adds genuinely non-obvious behavior: an empty list is a meaningful answer meaning only administrators can see the template's checklists, and a missing template 'refuses' rather than returning empty. It also clarifies that permissions govern checklist visibility, not template editing.

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?

The description is front-loaded with what the tool answers and ends with actionable sequencing advice to set_template_permissions. It is a little wordy in the middle clause about team roles, but every sentence carries real semantic content.

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 single-parameter list with no output schema, the description covers meaning, empty-vs-missing semantics, and relationship to the setter. It could say more about what a permission entry looks like, but that is a minor gap given annotations already cover safety.

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 coverage is 100% and the single parameter is already documented as 'The template's key, from list_templates. Required.' The description adds no further meaning about templateKey, so baseline 3 is appropriate.

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?

The description states exactly what the tool returns ('Who can see and run the checklists made from a template') and sharply scopes it away from template editing ('none of them lets anybody edit the template, which is a team role rather than a permission'). That distinction separates it from get_template and set_template_permissions without needing the schema.

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?

It gives explicit sequencing guidance ('Read this before set_template_permissions, which replaces the whole set'), which tells the agent when this read is a prerequisite. It does not name other plausible alternatives such as get_template or get_checklist_share, so the exclusion set is incomplete.

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

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