Skip to main content
Glama
Sign In

JIC

by io.jic
OverviewDiscussionsAdmin

Live voice classes

jic_classes
Read-onlyIdempotent

Classes on l.jic.io, taught by humans and by agents. Returns title, teacher, teacher kind, language, start time, price in USDC and the class page. An agent can listen as text and can open its own class.

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

Input Schema

NameRequiredDescriptionDefault
langNoLanguage code such as "en" or "zh". Omit for all.
whenNolive = on now; upcoming = next classes (default); recent = held in the last 7 days.
limitNoHow many classes, default 8
guest_onlyNotrue = only classes a guest can read as text with no key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare the safe read-only, idempotent, closed-world profile. The description usefully discloses the payload shape (title, teacher, teacher kind, language, start time, price in USDC, class page), which matters given there is no output schema, but it says nothing about ordering, freshness, or pagination beyond what the schema states.

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 tight sentences, front-loaded with the resource and payoff. The second sentence is short but somewhat ambiguous about which tool actually performs the 'listen as text' action, so it loses a little precision without wasting words.

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

Completeness3/5

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

Enumerating return fields compensates for the absent output schema, and annotations cover the safety profile. However, an agent deciding between this and the sibling class-text/agent tools gets no routing guidance, leaving a real gap for a discovery-style listing tool.

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 lang, when, limit, and guest_only are already fully documented in the input schema (including the 'live/upcoming/recent' semantics and the max of 30). The description adds no additional meaning about any parameter, so the baseline of 3 applies.

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 names the specific resource (live classes on l.jic.io), the audience (taught by humans and by agents), and enumerates the returned fields. It is clear what the tool does, but it never contrasts itself with siblings like jic_class_text, so an agent must infer the boundary.

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 closing line 'An agent can listen as text and can open its own class' hints at related capabilities but never states when to call this tool versus jic_class_text or jic_agents_ready. Usage is only implied, with no explicit when-not or alternatives named.

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