Skip to main content
Glama
Sign In

JIC

by io.jic
OverviewDiscussionsAdmin

Read a free trial class as text (no key)

jic_class_text
Read-onlyIdempotent

The guest pass for learning: read what the teacher said in a class, part by part, with the questions and answers. Works with no login for free trial classes (openToGuests is true in jic_classes). Ended classes stay readable. Pass the last n you got as "after" to continue.

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

Input Schema

NameRequiredDescriptionDefault
idYesClass id (10 hex characters) or class number, from jic_classes
afterNoReturn parts after this number. Default 0 = from the start.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added context is the value: authentication exemption for guest classes, the fact that ended classes remain readable, and pagination behavior. It does not describe result ordering or size limits, leaving a small gap.

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?

Three short sentences that front-load the core action and end with the pagination tip. The opening metaphor 'The guest pass for learning' is decorative filler that does not carry information, but the rest earns its place.

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 two-parameter read tool with no output schema, the description conveys what the payload looks like ('part by part, with the questions and answers') and how to page through it. That is nearly complete for this complexity; only return ordering/size details are absent.

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 coverage is 100% and both parameters are already documented in the schema, so the baseline is 3. The description only adds a procedural hint for 'after' ('the last n you got'), which is a marginal gain rather than new semantic detail about 'id' formats.

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 states a specific verb and resource: read a class transcript ('what the teacher said... part by part, with the questions and answers'), scoped to free trial classes sourced from jic_classes. It is clear what the tool returns, but it never names a sibling (e.g., jic_classes for listing) to differentiate itself explicitly, so it stops short of a 5.

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?

It gives clear applicability conditions: works without login only when openToGuests is true, and it supplies a concrete continuation procedure ('pass the last n you got as "after"'). No explicit when-not guidance or named alternatives are given, which keeps it below a 5.

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

All JIC toolsInspect
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