itu-mcp

Overview Schema Source Related Servers Discussions Admin

OBS Search Courses

obs_search_courses

Read-onlyIdempotent

Search exact course codes in public OBS or names and partial codes in the course archive. No login required; results do not show current-term offerings.

Instructions

Look up exact course codes in public OBS; name or partial-code searches use the labeled course archive. Results do not establish current-term offerings. No login required.

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": {
      "query": "<query>"
    },
    "name": "obs_search_courses"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv1.2.1Oct 14, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / properties

Added value: +{
+  "result": {
+    "additionalProperties": true,
+    "title": "Result",
+    "type": "object"
+  }
+}

addedOutput schema / required
```
Added value: +[
+  "result"
+]
```

changedOutput schema / title

Previous value: -"obs_search_coursesDictOutput"New value: +"obs_search_coursesOutput"

Addedv0.2.3Jul 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive. The description adds two things annotations cannot: no authentication is required, and results do not prove current-term offerings — a meaningful accuracy caveat for a public catalog lookup. It doesn't cover result count or pagination behavior beyond the default limit.

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?

Three tight clauses, front-loaded with the primary purpose then the routing rule then the caveat. No filler sentences and nothing repeated from the schema or annotations.

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?

An output schema exists, so return-value documentation is unnecessary. The description covers auth requirements, query interpretation, and result-validity limits; only the untended "limit" parameter leaves a small gap.

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 description coverage is 0%, so the description carries the burden. It clarifies that "query" expects an exact course code (not a name or fragment), which is genuinely useful, but says nothing about what "limit" controls. Partial compensation for a two-parameter tool.

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

Purpose5/5

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

States a specific verb and resource ("look up exact course codes in public OBS") and scopes the tool to exact-code queries only. It also implicitly contrasts with the archive tool for name/partial queries, so an agent can distinguish it from archive_search_courses without opening either schema.

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?

Explicitly routes non-exact queries elsewhere ("name or partial-code searches use the labeled course archive"), which is real when-not guidance. The alternative is described by role rather than exact tool name, so an agent must map it to archive_search_courses, which keeps this just short of a 5.

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

Deploy Server