Skip to main content
Glama
yatuk

itu-mcp

by yatuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Cafeteria Menu

get_cafeteria_menu
Read-onlyIdempotent

Retrieve İTÜ Portal lunch, dinner, or vegan cafeteria menus for a chosen date, including calories and allergens.

Instructions

Read a dated lunch/dinner or vegan menu from the İTÜ Portal (requires login), including calories and allergens.

Input Schema

NameRequiredDescriptionDefault
dateNo
mealNo
veganNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.2.1
    • addedInput schema / properties / date
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Date"
+}
    • addedInput schema / properties / meal
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Meal"
+}
    • addedInput schema / properties / vegan
      Added value: +{
+  "default": false,
+  "title": "Vegan",
+  "type": "boolean"
+}
    • 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: -"get_cafeteria_menuDictOutput"New value: +"get_cafeteria_menuOutput"
  2. Addedv0.2.3

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds valuable context beyond that by flagging the login requirement, but says nothing about rate limits, behavior on invalid/missing dates, or how a null date is interpreted.

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?

A single tightly-packed sentence with the resource front-loaded and the auth caveat placed inline. Every clause earns its place and nothing is padded.

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?

An output schema exists, so the description is right not to explain return values despite mentioning calories and allergens. What is missing is parameter-level completeness: with 0% schema coverage and no enums, the date and meal value formats should have been spelled out somewhere, and they are not.

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% and there are no enums, so the description carries the full burden. 'Dated' weakly implies the date parameter accepts a date and 'lunch/dinner or vegan' hints at meal/vegan values, but the date format (ISO? relative?) and valid meal strings are never specified, leaving the agent to guess on a tool where the schema offers nothing.

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 (Read) plus resource (dated lunch/dinner or vegan menu) and names the source (İTÜ Portal) and content (calories, allergens). No sibling tool covers cafeteria menus, so no differentiation is needed. It stops short of 5 only because the 'lunch/dinner or vegan' phrasing is slightly ambiguous about whether vegan is a meal category or a flag.

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?

The parenthetical '(requires login)' is a genuine precondition that tells the agent when this call will fail and may need an auth step first. However, it gives no guidance on defaults (all three params are optional with null defaults), no example date format, and no indication of what happens when date or meal is omitted.

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