Skip to main content
Glama

Add an instructor

add_instructor

Adds a name to the instructors that can be put on a class. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "name": "<name>"
    },
    "name": "add_instructor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world mutation, so the safety profile is covered. The description adds the useful fact that the write targets one specific venue and appends to a shared instructors pool. It does not disclose what happens on a duplicate name — relevant given idempotentHint=false — nor whether existing classes using the instructor are affected.

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 short sentences with the core action front-loaded and the scoping constraint second. No filler. The phrase 'Acts on one venue' is slightly oblique but compact.

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?

For a 3-parameter mutation with annotations and no output schema, the essentials are present: what is written, and to which venue. Missing pieces that matter for correct invocation are duplicate handling and whether the tool returns a created identifier, since no output schema exists to cover that.

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 67%: address and access_key are documented in the schema, name is not. The description partially compensates by clarifying that name is a person's name destined for the instructor roster and that address/access_key jointly identify the venue. It adds no format, casing, or uniqueness constraints on name.

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: adds a name to the roster of instructors assignable to a class. The second sentence adds scope (single venue, identified by address + access key). It does not explicitly distinguish itself from lookalike siblings such as add_staff, but the resource is named concretely enough to be selectable.

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?

The description supplies a prerequisite context — you must know the venue's address and access key — which implies this is a venue-scoped mutation rather than a global one. It gives no explicit when-to-use versus when-not guidance, and no mention of alternatives like add_staff or checking whether the instructor already exists.

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