Skip to main content
Glama

Create activity from template

create_activity_from_template
Destructive

Create a reviewed draft activity from a starter template.

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": {
      "template_key": "<template_key>"
    },
    "name": "create_activity_from_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
descriptionNo
price_centsNo
template_keyYes
meeting_locationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the safety profile is known. The description adds only that the result is a 'reviewed draft' rather than a live activity, but does not explain what draft state means, what 'reviewed' entails, or whether anything is irreversibly changed despite the destructiveHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no wasted words, but the brevity crosses into under-specification for a six-parameter mutation tool rather than serving clarity.

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?

For a destructive create with six parameters, 17% schema coverage, and no output schema, the description is far too thin. It says nothing about the returned draft, defaulting behavior for optional fields, or prerequisites such as obtaining a template_key.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17% – just business_id is documented. The description never explains template_key (the sole required parameter), nor what name, description, price_cents, or meeting_location do when supplied, and it gives no indication whether omitting them inherits values from the template.

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?

States a specific verb and resource: create a 'reviewed draft activity' from a 'starter template'. The 'from a starter template' qualifier implicitly separates it from the plain create_activity sibling, though it never names or contrasts that sibling explicitly.

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 choose this over create_activity, and no mention that template_key likely comes from list_activity_templates. The agent must infer the template-based workflow entirely from the tool name and one required parameter.

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