Skip to main content
Glama

load_toolset

Load the documentation and input schemas for a deferred toolset. Most ctlsurf tools are listed directly, but specialty toolsets are deferred to keep the tool list small. Call this when you need one of them, then invoke the returned tools via ctlsurf_call(tool_name, arguments).

Available toolsets:

  • dashboards (18 tools): Business: group dashboards with change-order, proposal/SOW and ticket cards, documents, rollups and pinned live blocks

  • datastore (14 tools): Agent working data: typed-column data tables with row operations, key-value state blocks, append-only logs

  • graphs (12 tools): Diagrams: react-flow node graphs, ER diagrams (DB schemas, API contracts, domain models), tree nodes

  • presentations (7 tools): Slide decks: create presentations, add structured slides from templates, export to .pptx

  • skills (17 tools): Agent playbooks: create, search, fork and share reusable workflow definitions

  • swimlanes (5 tools): Project timelines: swim-lane blocks with tasks in lanes, start/due dates, progress, status and dependencies

  • visuals (3 tools): Explanatory graphics for pages: steps, flows, comparisons, stats, bars, callouts, token strips, cycles, funnels. Use whenever a page explains something

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

Input Schema

NameRequiredDescriptionDefault
toolsetYesToolset to load

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / toolset / enum
      Previous value: -[
      -  "dashboards",
      -  "datastore",
      -  "graphs",
      -  "presentations",
      -  "skills",
      -  "swimlanes"
      -]New value: +[
      +  "dashboards",
      +  "datastore",
      +  "graphs",
      +  "presentations",
      +  "skills",
      +  "swimlanes",
      +  "visuals"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / toolset / enum
      Previous value: -[
      -  "dashboards",
      -  "datastore",
      -  "graphs",
      -  "presentations",
      -  "skills"
      -]New value: +[
      +  "dashboards",
      +  "datastore",
      +  "graphs",
      +  "presentations",
      +  "skills",
      +  "swimlanes"
      +]
  3. Changed1 schema field changed
    • changedInput schema / properties / toolset / enum
      Previous value: -[
      -  "datastore",
      -  "graphs",
      -  "presentations",
      -  "skills"
      -]New value: +[
      +  "dashboards",
      +  "datastore",
      +  "graphs",
      +  "presentations",
      +  "skills"
      +]
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly does: it discloses the return content (documentation plus input schemas), the reason for deferral (keeping the tool list small), and the required two-step invocation pattern. It does not say whether repeated loads are idempotent/cached or what loading costs in context, which is the only notable gap for a discovery tool.

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?

Front-loaded: the two operative sentences come first, and the catalog follows as a scannable bulleted list where every entry earns its place by aiding value selection. The trailing visuals clause ("Use whenever a page explains something") drifts slightly into vague marketing prose compared with the other entries' concrete feature lists.

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

Completeness5/5

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

For a one-parameter, no-output-schema discovery tool this is sufficient: the agent learns what it gets back (docs + schemas), why the tool exists, every legal argument value with tool counts, and how to act on the result via ctlsurf_call. Nothing needed to call it correctly is missing.

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

Parameters5/5

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

Schema coverage is 100% and the enum is fully enumerated, yet the description still adds real selection meaning beyond "Toolset to load" by pairing each allowed value with a tool count and a content summary (e.g. "swimlanes (5 tools): swim-lane blocks with tasks in lanes, start/due dates..."). This lets an agent choose the right enum value without guessing from the name.

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

Purpose5/5

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

"Load the documentation and input schemas for a deferred toolset" names a specific verb (load) and resource (deferred toolset docs + schemas), and immediately distinguishes it from the normally-listed tools by explaining why deferral exists. An agent can tell this is a discovery/unlock step, not a data operation.

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

Usage Guidelines5/5

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

It states the trigger ("Call this when you need one of them") and the mandatory follow-up path ("invoke the returned tools via ctlsurf_call(tool_name, arguments)"), effectively naming the sibling and the sequencing. The implicit when-not case (tools already listed directly) is also covered by the deferral explanation.

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