Skip to main content
Glama
saigyujikingyo-png

UoE Companion

by saigyujikingyo-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

study_collections

Read-onlyIdempotent

Search saved school resources, notes, and tags across local collections. Retrieve study materials linked to cached evidence quickly.

Instructions

Search saved school resources, notes and tags across local collections, linked to the latest cached evidence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryNo
detailNocompact
offsetNo
collectionNo
include_archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.5.0
    • removedInput schema / properties / collection / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / collection / oneOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / collection / title
      Removed value: -"Collection"
    • removedInput schema / properties / detail / title
      Removed value: -"Detail"
    • removedInput schema / properties / include_archived / title
      Removed value: -"Include Archived"
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / properties / offset / title
      Removed value: -"Offset"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"study_collectionsArguments"
  2. First observedv0.4.0

TDQS

C2.3/5.0
Behavior2/5

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

Annotations declare read-only, idempotent, non-destructive behavior, so safety is covered. The description adds almost nothing beyond that: it doesn't explain pagination, default result detail, handling of archived items, or what 'linked to the latest cached evidence' actually means operationally.

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?

A single, compact sentence with no filler. It is front-loaded with the core action, though the trailing clause about cached evidence could be clearer.

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

Completeness2/5

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

For a tool with six undocumented parameters, no output schema, and ambiguous behavioral hints, the description is inadequate. It does not explain what constitutes a 'collection', how results are returned, or how the cached evidence linkage affects results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not mention any of the six parameters (limit, query, detail, offset, collection, include_archived). With no parameter documentation anywhere, the description fails to compensate for the severe coverage gap.

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

Purpose3/5

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

States a specific verb (Search) and resource (saved school resources, notes, tags), which gives partial clarity. However, the phrase 'linked to the latest cached evidence' is vague and confusing, and the description doesn't clearly distinguish this tool from siblings like study_search or study_evidence.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as study_search or study_evidence. The description implies searching saved collections but offers no context, prerequisites, or exclusions.

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