Skip to main content
Glama
Sign In
the-teacher

the-teacher

by outlast85
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

load_target

Load a learning target from a JSON template file to define observable claims and structure your study session.

Instructions

Load a Target from a JSON template file and set it as the current target. Defaults to the shipped example (zero personal data). Validates via build_target.

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_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNotemplates/example.json

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden. It discloses that the tool sets the current target and performs validation, but lacks details on side effects (e.g., overwriting), error handling, or access requirements.

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

Conciseness5/5

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

The description is two sentences with no filler. The first sentence states the core action; the second provides default and validation context. Every sentence is essential.

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 tool with one parameter, no output schema, and no annotations, the description covers purpose, default, and validation. It could briefly mention return behavior, but overall it is adequate.

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

Parameters4/5

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

Schema description coverage is 0%, so the description compensates by explaining the parameter as a file path for a JSON template and noting the default. This adds meaning beyond the schema, though it could clarify format constraints.

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?

The description clearly states the action 'Load a Target from a JSON template file' and 'set it as the current target', specifying the resource and outcome. It also distinguishes from siblings like set_target by mentioning file-based loading and validation via build_target.

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

Usage Guidelines4/5

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

The description implies usage for loading a target from a file, with a useful default example. However, it does not explicitly state when not to use this tool or mention alternatives like set_target.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools