Skip to main content
Glama
Sign In
LearningSuite MCP Server

LearningSuite MCP Server

by fabienbutz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

learningsuite_find_groups_by_name

Search groups by name to locate specific groups and access their details for management within LearningSuite.

Instructions

Find groups by name

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

Input Schema

NameRequiredDescriptionDefault
nameYesGroup name to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain whether the search is exact or partial, case sensitivity, pagination, return format, or error handling. The agent remains unaware of key behavioral traits.

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?

The description is extremely concise with zero fluff, using a single imperative sentence. However, it is arguably too minimal, lacking additional structured guidance that would improve clarity without being verbose.

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

Completeness2/5

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

The tool is simple (one parameter, no output schema), but the description does not cover essential context such as matching behavior, whether the operation is read-only, or how results are returned. With no annotations to compensate, the description is insufficient for complete understanding.

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?

The schema already documents the single parameter 'name' with description 'Group name to search for', giving 100% coverage. The tool description merely repeats 'by name' and adds no additional semantic detail, so it does not elevate beyond the baseline.

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 tool finds groups by name, with a specific verb (Find) and resource (groups), and distinguishes itself from sibling tools like list_groups by the by-name filter. This is specific and unambiguous.

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 implies the tool is used when searching for a group by its name, but does not explicitly state when to use it over alternatives like list_groups or provide exclusions. The usage context is inferred but not explicitly guided.

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