Skip to main content
Glama
Sign In

uNotes

by net.unotes
OverviewDiscussionsAdmin

Get lecture

get_lecture
Read-onlyIdempotent

Open one of the user's lectures: title, status, notes, transcript and recording details.

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": {
      "lectureId": "<lectureId>"
    },
    "name": "get_lecture"
  }
}

Input Schema

NameRequiredDescriptionDefault
lectureIdYesLecture id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already state that this is read-only, idempotent, non-destructive, and not open-world. Beyond that, the description adds useful payload context by naming the fields an agent can expect: title, status, notes, transcript, and recording details. It could be stronger by noting whether transcripts or recordings may be unavailable.

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 a single efficient sentence with no filler. It front-loads the action and resource, then immediately lists the useful return contents.

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 no output schema, the description helpfully enumerates the main data returned by the tool. Annotations cover the safety profile and the sole parameter is fully documented in the schema. It is nearly complete, with only minor gaps around error behavior or nullable fields such as transcripts.

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?

There is only one parameter, lectureId, and the schema already documents it at 100% coverage. The description implies that the tool operates on a single lecture, but it does not add format, source, or validation details beyond the schema. A baseline 3 is appropriate.

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 a specific verb and resource: opening one of the user's lectures. It also lists the returned fields (title, status, notes, transcript, recording details), making the resource scope clear. It does not explicitly differentiate itself from nearby siblings such as list_lectures or get_lecture_audio.

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 phrase 'one of the user's lectures' implies this is a single-item retrieval tool rather than a list tool, and the required lectureId reinforces that. However, there is no explicit guidance about when to use this instead of list_lectures, get_lecture_audio, or other lecture-related siblings.

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

All uNotes 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