Skip to main content
Glama

Load a toolset

enable_toolset
Read-onlyIdempotent

[read-only] Returns the full definitions (description and input schema) of every tool in one toolset, so you can call them. Call them by name, or through call_tool if your client only calls listed tools. To list a toolset on every connection, add ?toolsets=core, to the MCP URL.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe toolset, e.g. "ads". One of: core, publishing, campaigns, analytics, studio, ads, stores, ops.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the '[read-only]' tag is largely redundant. What the description does add is genuinely behavioral: the exact payload returned (full definitions and input schema of every tool in the set) and the downstream call path with a fallback for clients that can only call listed tools. It stops short of noting any size or result-limit considerations.

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?

Three short sentences, front-loaded with what is returned and immediately followed by the invocation path, so no scanning is required. The bracketed '[read-only]' prefix duplicates an annotation and is the one piece of avoidable text. There is no rambling or filler beyond that.

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 one-parameter, fully annotated, non-destructive read tool with no output schema, the description covers purpose, return payload, and invocation path sufficiently to call it correctly. The gap is whether repeated calls stack, and whether the response can be large. Both matter here, but neither is fatal.

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 'name' parameter carries a full enum plus a description, so the schema does the heavy lifting and a 3 baseline applies. The description contributes one extra hint, '?toolsets=core,<name>', implying core is normally paired with the chosen toolset, but it doesn't explain whether loading is additive, cumulative, or replaced on repeat calls.

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: returns full definitions (description + input schema) for every tool in one toolset, plus the reason ('so you can call them'). An agent can tell this is a toolset-loading/enumeration tool rather than an execution tool. It does not explicitly contrast with siblings like describe_tool or search_tools, which is the only thing separating it from 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 Guidelines3/5

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

Guidance is about what to do after loading ('call them by name, or through call_tool if your client only calls listed tools') and about a persistent alternative via the ?toolsets= URL parameter. That's useful context, but it never states plainly when to choose enable_toolset over search_tools/describe_tool, or that it should be called when a needed tool isn't in the listed set. Usage is implied rather than prescribed.

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