Skip to main content
Glama

List trainers

list_trainers
Read-onlyIdempotent

The trainers: name, title, short bio, the courses each teaches, url.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: en, de or sr. Default en.en

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description's only added value is that it discloses the return fields - name, title, bio, taught courses, url - which matters because no output schema exists, but it says nothing about whether all trainers are returned, ordering, or pagination.

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

Conciseness3/5

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

It is short and front-loaded with the resource, but it is a bare noun-phrase fragment with no verb, which reads as under-specification rather than deliberate conciseness. Not a single word is wasted, but the structure is too telegraphic to be clear.

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 simple read-only list tool with one optional enum parameter and rich annotations, the field enumeration supplies most of what an agent needs, especially since there is no output schema. It still omits whether the full trainer set is returned and how the lang parameter changes the result, leaving a modest gap.

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?

There is a single optional parameter (lang) with an enum and 100% schema description coverage, so the schema fully documents it. The description adds nothing about language behavior, which is the baseline-3 case when the schema does the work.

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

Purpose3/5

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

The fragment 'The trainers: name, title, short bio, the courses each teaches, url' identifies the resource (trainers) and enumerates the fields returned, which goes slightly beyond the name/title. However, there is no verb and no statement that it lists all trainers, so the purpose must be inferred from the tool name rather than read from the description.

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 use this tool versus siblings such as get_course or search_courses, and no mention of prerequisites, scope, or exclusions. The read-only nature is only implied by the resource name; nothing in the text routes an agent to or away from this tool.

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