Skip to main content
Glama

List activity templates

list_activity_templates
Read-only

List starter activity templates for the business categories.

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

Input Schema

NameRequiredDescriptionDefault
categoryNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds essentially nothing beyond that: no pagination, no result volume, no statement of whether templates are category-scoped or global, and no hint about how the returned templates feed into create_activity_from_template.

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?

A single short sentence with no filler and the scope front-loaded. It is efficient but borders on under-specified rather than genuinely tight.

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?

With no output schema, the description should explain what a template record looks like and how to act on it, and it does neither. For a list tool sitting at the head of a create-from-template workflow, an agent is left guessing about result shape and next step.

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 only 50% (business_id is documented, category is not), so the description carries partial burden. "For the business categories" implies the category parameter filters by business category, which is a small but real addition beyond the bare schema. It still does not state whether category is a slug, name, or ID, nor whether both parameters can be combined.

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?

The description gives a specific verb and resource ("List ... activity templates") and adds the scope qualifier "starter ... for the business categories", so an agent knows this returns pre-built templates rather than live activities. It does not distinguish itself from siblings such as list_activities or create_activity_from_template, which the rubric requires for a 5.

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 when-to-use guidance is offered: nothing says this is the discovery step before create_activity_from_template, and nothing excludes list_activities. The agent must infer the workflow from the tool name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources