plat.plus

Sessions

get_sessions

Read-onlyIdempotent

Lists a Course's Sessions with their dates and places. With a sessionId, reads that Session's page once it is open to the person.

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

Input Schema

Name	Required	Description	Default
`courseId`	Yes	The Course's id, from list_courses
`sessionId`	No	A Session's id, from a first call without it, to read its page

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare this as a read-only, idempotent, closed-world operation. The description adds that listing includes dates and places and that session-page access depends on it being "open to the person," but that access condition is vague and no pagination or failure behavior is described.

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

Conciseness5/5

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

The description is two tightly written sentences, front-loading the primary listing behavior before explaining the optional sessionId mode. There is no redundant or filler wording.

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?

For a simple read-only tool with rich annotations and full schema parameter coverage, the description covers both operating modes and the fields returned by listing. The remaining gap is the vague access condition and absence of pagination details, but these are relatively minor.

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?

Schema description coverage is 100%, so both parameters are already documented in the schema. The description reinforces that sessionId switches from list mode to single-session read mode, but the schema's own sessionId description already conveys this, and the added "open to the person" detail is ambiguous.

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

Purpose4/5

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

The description uses a specific verb and resource: "Lists a Course's Sessions" and then describes the single-session mode. It clearly distinguishes the two behaviors of the tool, though it does not explicitly differentiate against sibling tools.

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 description gives clear context for when to supply sessionId: to read that Session's page instead of listing all Sessions. It does not state exclusions or compare against alternative tools, but the two usage modes are clear.

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

All plat.plus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?