Skip to main content
Glama
saigyujikingyo-png

UoE Companion

by saigyujikingyo-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

study_read_service

Reads university service pages and files via your authenticated SSO session, returning a job_id to poll. Retrieve course, programme, assessment, or enrolment content without changing school records.

Instructions

Read a school service through the plugin-owned SSO session, returning a job_id to poll. Use service ids from study_services. Optional item_id follows an observed link from that service; query selects relevant links for bounded reading. For formal enrolments use service_id=euclid and section=Courses. The section enum lists observed read-only EUCLID labels. Captures text and links in the central search index. Does not submit forms, applications or change school records.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
item_idNo
sectionNo
max_pagesNo
service_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv0.5.0
    • removedInput schema / properties / item_id / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / item_id / oneOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / item_id / title
      Removed value: -"Item Id"
    • removedInput schema / properties / max_pages / title
      Removed value: -"Max Pages"
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / properties / section / anyOf
      Removed value: -[
-  {
-    "enum": [
-      "Programme",
-      "Courses",
-      "Assessment",
-      "Documents",
-      "Progression & awards",
-      "Scholarships and funding",
-      "Personal details",
-      "Immigration details"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / section / oneOf
      Added value: +[
+  {
+    "enum": [
+      "Programme",
+      "Courses",
+      "Assessment",
+      "Documents",
+      "Progression & awards",
+      "Scholarships and funding",
+      "Personal details",
+      "Immigration details"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / section / title
      Removed value: -"Section"
    • removedInput schema / properties / service_id / title
      Removed value: -"Service Id"
    • removedInput schema / title
      Removed value: -"study_read_serviceArguments"
  2. First observedv0.4.0

TDQS

A4/5.0
Behavior4/5

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

Discloses behavior beyond the annotations: the SSO-session ownership, the job_id polling model, and the side effect of capturing text and links into the central search index (which is consistent with readOnlyHint=false). It does not state permissions or rate/scope limits, but the async and persistence traits are genuinely useful context.

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?

Front-loaded with the core action and return contract, then layers the parameter guidance and the negative constraint. Dense but every sentence contributes; no filler.

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 5-param, no-output-schema tool it covers the return contract (job_id to poll), the SSO context, indexing side effect, and the read-only boundary. The gap is max_pages semantics/default and any indication of job result shape, which the annotations alone do not supply.

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

Parameters4/5

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

With 0% schema description coverage the description must carry the load, and it does for most parameters: service_id provenance, item_id as an observed link, query as link selection, and the meaning of the section enum including the euclid/Courses case. It omits max_pages entirely, leaving one of five parameters undocumented.

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?

States a specific verb+resource ('Read a school service') plus the async contract ('returning a job_id to poll') and the SSO mechanism. It is clearly distinguishable from write siblings, though it does not explicitly contrast with other read siblings like study_read_resource or study_collect.

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?

Gives concrete routing ('Use service ids from study_services', 'For formal enrolments use service_id=euclid and section=Courses') and an explicit exclusion ('Does not submit forms, applications or change school records'). No guidance, however, on when to prefer this over the other read tools in the sibling set.

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