Skip to main content
Glama
saigyujikingyo-png

UoE Companion

by saigyujikingyo-png
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

study_services

Read-onlyIdempotent

Find central university services including MyEd, Learn, EUCLID, timetable, library, careers/internships, events, and support, with dated coverage notes to verify access.

Instructions

List the central school service directory: MyEd, Learn, EUCLID student records, timetable, library, careers/internships, events and support. Includes dated per-service coverage; an entry alone is not proof of access.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNo
detailNocompact
localeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.5.0
    • removedInput schema / properties / detail / title
      Removed value: -"Detail"
    • addedInput schema / properties / locale
      Added value: +{
+  "default": null,
+  "oneOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • removedInput schema / properties / query / title
      Removed value: -"Query"
    • removedInput schema / title
      Removed value: -"study_servicesArguments"
  2. First observedv0.4.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare the safe read-only profile, but the description adds genuinely new behavioral context: results include dated per-service coverage (freshness metadata) and the warning that presence in the list does not imply access. That caveat meaningfully changes how an agent should interpret results, which annotations cannot convey.

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 sentences, front-loaded with the action and resource, with no filler. The long category enumeration is informative rather than wasteful, though it is the bulk of the text and could be trimmed for a tool whose return values carry that detail.

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?

There is no output schema, so the description must carry the return-value burden; it partly does by disclosing dated per-service coverage. But it leaves all three parameters unexplained and does not describe the result shape beyond the category list, leaving gaps for a 3-parameter discovery tool.

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

Parameters2/5

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

Schema description coverage is 0% for three parameters (query, detail enum, locale), and the description mentions none of them — no guidance on search syntax, what compact vs. full returns, or locale behavior. The enumerated service categories describe content, not parameter semantics, so the description fails to compensate for the coverage gap.

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 gives a specific verb ("List") and a concrete resource ("the central school service directory") with enumerated contents (MyEd, Learn, EUCLID, timetable, library). An agent can tell this is the broad directory-listing tool rather than a reader like study_read_service. It never names those siblings explicitly, so no differentiation credit beyond the resource scoping.

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?

Usage is implied: this is the directory/discovery surface, and the caveat "an entry alone is not proof of access" hints that a follow-up read step is needed. However, no explicit when-to-use, when-not, or named alternative is given, so the agent must infer the routing.

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