Skip to main content
Glama
saigyujikingyo-png

UoE Companion

by saigyujikingyo-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

study_collect

Save school pages, course resources, internships or events to a local collection with tags and notes. Repeating an item updates its entry and archives locally without changing school records.

Instructions

Save an observed school page, course resource, internship or event to a local collection with tags/notes. Repeating the same item and collection updates that entry. archived=True archives it locally; no school record changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
notesNo
item_idYes
archivedNo
collectionNoInbox

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • removedInput schema / properties / archived / title
      Removed value: -"Archived"
    • changedInput schema / properties / collection / default
      Previous value: -"收件箱"New value: +"Inbox"
    • removedInput schema / properties / collection / title
      Removed value: -"Collection"
    • removedInput schema / properties / item_id / title
      Removed value: -"Item Id"
    • removedInput schema / properties / notes / title
      Removed value: -"Notes"
    • removedInput schema / properties / tags / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / tags / oneOf
      Added value: +[
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / tags / title
      Removed value: -"Tags"
    • removedInput schema / title
      Removed value: -"study_collectArguments"
  2. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnly=false, destructive=false, openWorld=false. The description adds genuine behavioral value beyond that: upsert semantics ("Repeating the same item and collection updates that entry"), the meaning of archived=True, and an explicit impact boundary (no school record changes).

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, front-loaded with the action and item types, then upsert behavior, then the safety boundary. No filler, though the archived clause is slightly terse.

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 0%-coverage schema with no output schema, the description adequately covers what gets saved, upsert behavior, archiving, and the blast radius. It omits what the call returns and any permission requirements, which are minor gaps.

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 0%, so the description must carry the load. It explains archived=True, tags/notes, and the collection target, which covers most parameters, but says nothing about item_id's expected form or the "Inbox" default exposed in the schema.

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?

Specific verb ("Save") plus enumerated resources (school page, course resource, internship, event) and a destination (local collection). It is clearly a write-to-collection tool, though it never names a sibling like study_collections or study_capture to sharpen 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?

Implies when to use it (saving an observed item) and clarifies scope with "no school record changes," but gives no explicit when-not or alternative (e.g., how it differs from study_capture or study_collections).

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