Skip to main content
Glama
oliverhruby

EduPage MCP Server

by oliverhruby
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

send_message

Destructive

Send a message to an EduPage recipient and post it to their timeline. Use recipient IDs from the roster to contact students or teachers.

Instructions

Send a message to a recipient. Writes: posts a new message on the recipient's timeline.

Args: recipient_id: EduPage id like 'Student123' or 'Teacher456' (see get_roster). body: Message text. Must not be empty. subdomain: School to query (defaults to the active subdomain).

Returns: dict: {'sent': True, 'timeline_id': }.

Notes: - Recipient ids come from get_roster(roster_type='students'|'teachers') or get_my_students.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
subdomainNo
recipient_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / subdomain / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / subdomain / type
      Removed value: -"string"
  2. First observedv0.4.6

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds the destination of the write (recipient's timeline) and the non-empty body constraint, but says nothing about irreversibility, visibility to the recipient, or rate limits for a destructive write.

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?

Front-loads the action and its side effect, then uses tidy Args/Returns/Notes sections where each line carries information. Slightly verbose in structure, but no sentence is wasted.

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

Completeness4/5

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

With only three parameters, no output schema, and no enums, the description covers what an agent needs: all three arguments, the return shape ({'sent': True, 'timeline_id': <id>}), and where ids originate. Only the absence of failure/error behavior keeps it from being fully complete.

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

Parameters4/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, and it largely does: it gives the recipient_id format and concrete examples ('Student123'/'Teacher456') plus its source tool, states body must not be empty, and explains that subdomain defaults to the active subdomain.

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+resource ("Send a message to a recipient") and immediately clarifies the effect: it posts onto the recipient's timeline. This cleanly separates it from read-oriented siblings like get_timeline and get_roster, so an agent knows it is a write tool without opening the schema.

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?

Usage is only implied: the Notes tell the agent where recipient ids come from (get_roster, get_my_students), which is a useful precondition, but there is no explicit statement of when to use this tool versus alternatives or when not to use it.

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