Skip to main content
Glama

get_messages

Retrieve personal and course messages from an Open eClass inbox or outbox, with optional search and result limits for quick review.

Instructions

Personal and course messages. mailbox is 'inbox' or 'outbox'.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
searchNo
mailboxNoinbox

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses almost nothing: no read-only confirmation, no permission or auth requirements, no note on ordering, pagination, or whether 'limit' truncates results. The single behavioral hint is the mailbox enumeration, which is thin for a 3-parameter retrieval tool.

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 no filler and the resource statement front-loaded. The brevity is genuine economy rather than padding, though the second sentence spends the only detailed content on the least ambiguous parameter.

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?

An output schema exists, so return values needn't be described, but for a three-parameter tool with zero schema documentation the description leaves the two most consequential parameters ('search', 'limit') undefined and offers no guidance relative to the singular 'get_message' sibling. It is not complete enough for reliable invocation without trial and error.

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%, so the description must compensate for all three parameters, yet it only explains 'mailbox' as 'inbox' or 'outbox'. 'limit' (default 30) and 'search' (default empty string) get no meaning at all – an agent must infer whether search matches subject, body, or sender, and what the limit bounds.

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 'Personal and course messages' identifies the resource domain and adds that messages span both personal and course contexts, but it contains no verb (list/get/read) and no scope statement. It also does nothing to distinguish this from the sibling 'get_message' (singular), so an agent cannot tell which one returns a collection.

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 when-to-use guidance at all: no condition for choosing this tool over 'get_message', no mention of prerequisites, and no exclusion of any case. The only guidance-like text explains valid mailbox values, which is a parameter detail rather than a usage condition.

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