Skip to main content
Glama
Sign In

Hugging Bay

by io.github.barneywohl
OverviewDiscussionsAdmin

get_teach_template

Read-only

Read a local Teach template. Examples stay local; hosted tools do not train.

Input Schema

NameRequiredDescriptionDefault
idYes
baseNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedOutput schema / additionalProperties
      Removed value: -true
  2. Changed2 schema fields changed
    • removedInput schema / properties / base / description
      Removed value: -"Selected starting model id; carried into the shared first task."
    • removedInput schema / properties / id / description
      Removed value: -"Artifact or record id returned by a previous read."
  3. Changed1 schema field changed
    • addedInput schema / properties / base
      Added value: +{
+  "description": "Selected starting model id; carried into the shared first task.",
+  "enum": [
+    "hf-model-qwen-qwen2-5-0-5b-instruct",
+    "hf-model-qwen-qwen3-1-7b",
+    "hf-model-qwen-qwen3-4b"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • removedInput schema / properties / base
      Removed value: -{
-  "description": "Selected starting model id; carried into the shared first task.",
-  "enum": [
-    "hf-model-qwen-qwen2-5-0-5b-instruct",
-    "hf-model-qwen-qwen3-1-7b",
-    "hf-model-qwen-qwen3-4b"
-  ],
-  "type": "string"
-}
  5. Changed1 schema field changed
    • addedInput schema / properties / base
      Added value: +{
+  "description": "Selected starting model id; carried into the shared first task.",
+  "enum": [
+    "hf-model-qwen-qwen2-5-0-5b-instruct",
+    "hf-model-qwen-qwen3-1-7b",
+    "hf-model-qwen-qwen3-4b"
+  ],
+  "type": "string"
+}
  6. Changed1 schema field changed
    • changedInput schema / properties / id / enum
      Previous value: -[
-  "payment-risk",
-  "ticket-triage",
-  "invoice-fields",
-  "replies-in-our-voice",
-  "contract-clause-check",
-  "product-tagging"
-]New value: +[
+  "refund-fraud",
+  "payment-risk",
+  "ticket-triage",
+  "invoice-fields",
+  "replies-in-our-voice",
+  "contract-clause-check",
+  "product-tagging"
+]
  7. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds the useful local-only/data-handling caveat ("Examples stay local; hosted tools do not train"), but says nothing about what the template contains or how the base parameter affects behavior.

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 compact sentences with the core action front-loaded and no wasted words. The trailing privacy sentence is somewhat cryptic out of context but short enough not to harm structure.

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

Completeness3/5

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

The output schema exists, so return values needn't be explained, and annotations cover safety. Still, for a two-parameter tool with zero schema descriptions, the definition leaves the agent guessing about the base parameter and the purpose of templates.

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

Parameters2/5

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

Schema description coverage is 0% and the description explains neither parameter. The id enum values hint at the template set, but the meaning of the base parameter (presumably selecting a model variant for the template) is left entirely undocumented.

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?

The description states a specific verb and resource ("Read a local Teach template"), which is enough to distinguish it from siblings like list_teach_bases or get_model. However, it never clarifies what a "Teach template" actually is, so the agent must infer its nature from the enum ids.

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?

There is no guidance on when to call this versus list_teach_bases (to discover ids) or get_model (for the base models). The second sentence is a privacy statement, not usage direction, and no prerequisites or alternatives are named.

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

All Hugging Bay toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources