Skip to main content
Glama

Publish activities

publish_activities
Destructive

Publish reviewed activities, or all ready reviewed activities.

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

Input Schema

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

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 flag destructiveHint=true and readOnlyHint=false, so the description needed to add what publishing actually changes, whether it is reversible, or what happens to already-published activities. Instead it says nothing beyond the annotation surface, leaving the destructive side effect unexplained.

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 the resource up front and no filler. It is efficient, though the brevity comes at the cost of specificity rather than being tight and informative.

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?

This is a destructive, zero-required-parameter batch operation with no output schema and half its parameters undocumented. The description should clarify the default all-publish behavior when activity_ids is omitted and the consequences of the destructive action, and it does neither.

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 50%: business_id is documented in the schema, while activity_ids is not. The phrase 'or all ready reviewed activities' weakly implies that omitting activity_ids publishes everything eligible, which adds some meaning, but the 'ready reviewed' condition and the all-at-once behavior remain ambiguous.

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

Purpose3/5

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

The verb 'publish' and resource 'activities' are named, but the qualifier 'reviewed activities' is never defined, so the agent cannot tell which activity state qualifies. It also draws no boundary against siblings like create_activity or list_activities.

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?

The description hints at two modes (publish specified activities, or all 'ready reviewed' ones) but gives no when-to-use guidance, no prerequisites about review state, and no explicit alternative to prefer for other cases.

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