Skip to main content
Glama
Sign In
Revel Digital MCP Server

Revel Digital MCP Server

Official
by RevelDigital
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gettemplategroups

Retrieve template groups from your account, with optional filtering by template ID, pagination, and hierarchical data format.

Instructions

Gets template groups in the account.

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

Input Schema

NameRequiredDescriptionDefault
idNoOptional template id to filter by
pageNoOptional number of page to return
takeNoOptional number of items to return
treeNoOptional hierarchical data format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.20

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. No information about pagination, filtering, data format, or side effects.

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?

One sentence is very concise. However, it could be slightly more informative without adding length, leading to a minor deduct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and all parameters optional, the description lacks crucial context about return format, pagination defaults, and the meaning of the 'tree' parameter. This leaves agents with gaps.

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% with parameter descriptions. The tool description adds no additional meaning beyond what is in the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool retrieves template groups, distinguishing it from sibling tools like 'gettemplates' which gets templates. However, the verb 'Gets' is generic and could be more specific (e.g., 'Lists').

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'gettemplatebyid' or 'gettemplates'. The description does not mention context or exclusions.

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