Skip to main content
Glama

Get an example group-maker input

get_group_example
Read-only

Return the full input JSON of one example, in exactly the shape make_groups accepts: 'classroom' = 30 students, 6 groups, together and apart codes, categorical and numeric fields, blanks; 'teams' = 20 colleagues in 4 teams balanced on a numeric skill and a role. Edit it (people, fields, priorities, number of groups) to match the user's situation.

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": {
      "kind": "<kind>"
    },
    "name": "get_group_example"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds the behaviorally important fact beyond the annotations: the returned JSON is in the exact shape make_groups accepts and is intended to be edited, which tells the agent the payload is a valid, mutable template rather than a finished result.

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 the verb and return shape before the per-kind detail and the edit instruction. The semicolon-heavy enumeration of the two example kinds is dense but every element conveys distinct content, so nothing is wasted.

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

Completeness5/5

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

There is no output schema, and the description compensates by stating exactly what comes back (full input JSON in make_groups' accepted shape) plus how to use it. For a single-enum, read-only helper this covers everything an agent needs to call it correctly.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it does: 'classroom' is spelled out as 30 students, 6 groups, together/apart codes, categorical and numeric fields and blanks, while 'teams' is 20 colleagues in 4 teams balanced on numeric skill and role. An agent can pick the right enum value without guessing what the example contains.

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 ("Return the full input JSON of one example") and ties it to a named consumer ("exactly the shape make_groups accepts"), which immediately distinguishes it from make_groups, get_group_result and check_request. The two enum values are also characterized in concrete terms.

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 closing instruction, "Edit it (people, fields, priorities, number of groups) to match the user's situation," makes clear this is a starting template to be modified before calling make_groups. What is missing is an explicit trigger such as "call this first when the user has no existing input JSON," so the when-not condition remains implied rather than stated.

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