Skip to main content
Glama

Extralingo

by com.extralingo
OverviewDiscussionsAdmin

list_starting_dates

Read-onlyIdempotent

Allowed course start dates (typically Mondays) for a school. Use startDate values in list_courses and configuration.startDate.

Input Schema

NameRequiredDescriptionDefault
localeNoResponse language and site context. One of en, nl, da, sv.
school_idYesCraft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID.

Output Schema

NameRequiredDescriptionDefault
datesNoBookable course start dates (typically Mondays, YYYY-MM-DD strings).
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedOutput schema / properties / data
      Removed value: -{
-  "additionalProperties": true,
-  "type": "object"
-}
    • addedOutput schema / properties / dates
      Added value: +{
+  "description": "Bookable course start dates (typically Mondays, YYYY-MM-DD strings).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed5 schema fields changed
    • addedInput schema / properties / locale / description
      Added value: +"Response language and site context. One of en, nl, da, sv."
    • addedInput schema / properties / locale / examples
      Added value: +[
+  "en",
+  "nl",
+  "da",
+  "sv"
+]
    • addedInput schema / properties / school_id / description
      Added value: +"Craft CMS school entry id from search_language_schools hits (field school_id). Not the CRM UUID."
    • addedInput schema / properties / school_id / examples
      Added value: +[
+  12345
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "success": {
+      "const": true
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the 'typically Mondays' domain caveat; no auth, rate-limit, or pagination details are given.

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?

Two tight sentences, with the resource definition and the 'typically Mondays' caveat front-loaded before the downstream consumption hint. 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 simple read-only lookup with a fully documented 2-param schema and an output schema, the description covers purpose, value semantics, and cross-tool usage adequately. Only minor gaps (e.g., ordering of returned dates) remain.

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 100%, and the schema already explains locale enum values and that school_id is the Craft CMS entry id (not the CRM UUID). The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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+resource ('Allowed course start dates ... for a school') and scopes it to a single school, which cleanly distinguishes it from the broader sibling list_courses. The cross-reference to where these values are consumed makes the tool's role unambiguous.

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 tells the agent what to do with the result: 'Use startDate values in list_courses and configuration.startDate,' which is real chaining guidance. It does not, however, name an alternative tool or state when *not* to call this one.

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

All Extralingo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources