Skip to main content
Glama

load_sample_clients

Add a set of demo clients with example data so the coach can explore the app. Only for solo coaches with none loaded (check get_sample_clients_status). (confirm-gated: previews until confirm: true)

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

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only tell the agent this is a non-readonly, non-destructive, closed-world operation. The description adds real behavioral context beyond that: the confirm-gated preview-then-execute flow and the eligibility constraint (solo coaches, none loaded). It stops short of saying what happens if data is already loaded or whether the seeded records are marked/traceable.

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?

Two sentences, front-loaded with purpose and followed by the constraint and gating note. The parenthetical confirm explanation partly duplicates schema text, which is the only minor redundancy.

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, non-destructive seeding tool with no output schema, the description covers purpose, eligibility, the status-check prerequisite, and the confirmation mechanism. Remaining gaps (post-execution state, reversibility via remove_sample_clients) are minor given the sibling set.

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 'confirm' parameter already documents the preview-vs-execute semantics, so the schema does the heavy lifting. The description restates the gating at a workflow level, which is helpful framing but adds no new meaning about the parameter itself; baseline 3 applies.

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?

States a specific verb and resource ('Add a set of demo clients with example data') plus the intent ('so the coach can explore the app'). This makes it trivially distinguishable from sibling tools like remove_sample_clients and get_sample_clients_status without opening any schema.

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?

Explicitly bounds usage: 'Only for solo coaches with none loaded' supplies both a when and a when-not condition, and it names the sibling to check first ('check get_sample_clients_status'). This is about as close to an explicit routing rule as a description gets.

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.