Skip to main content
Glama

remoet-mcp

by io.github.remoet-labs
OverviewDiscussionsAdmin

Save Education

save_education

Add or update an education entry (upsert). Omit id to create (institution is required); pass an id (from get_profile) to update, changing only the fields you send. Ask about degrees, bootcamps, and notable certifications. Confirm approximate dates with the user rather than guessing; don't fabricate. Check get_profile first to avoid duplicates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoPresent: update this education entry (only the fields you pass change). Omit: create a new one (institution is required to create).
endDateNoEnd date: a date, e.g. "2024-01-15"
isCurrentNoWhether you are currently studying here (default false on create)
startDateNoStart date: a date, e.g. "2024-01-15"
studyLevelNoLevel of study: HIGH_SCHOOL, ASSOCIATE, BACHELOR, MASTER, DOCTORATE, BOOTCAMP, or OTHER
descriptionNoDescription of studies, achievements, etc.
institutionNoInstitution name (e.g. "MIT", "Lund University")
fieldOfStudyNoField of study (e.g. "Computer Science")
institutionUrlNoInstitution website URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / endDate / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / endDate / description
      Previous value: -"End date (ISO 8601)"New value: +"End date: a date, e.g. \"2024-01-15\""
    • addedInput schema / properties / institution / minLength
      Added value: +1
    • changedInput schema / properties / startDate / anyOf
      Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / startDate / description
      Previous value: -"Start date (ISO 8601)"New value: +"Start date: a date, e.g. \"2024-01-15\""
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations are all false, so the description carries the full burden. It discloses that updates only change sent fields, that institution is required on create, and advises confirming dates and not fabricating—useful behavioral context beyond the schema.

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?

Compact and front-loaded: the core upsert concept comes first, then conditional logic, then conversational guidance, then a pre-check. Every sentence earns its place with zero fluff.

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 write operation with no output schema, it covers the essential behaviors (create/update), conditional requirements, and user-interaction guidance. Missing minor details like return value, but not necessary given no output schema.

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?

Schema coverage is 100% (all 9 parameters have descriptions), so the baseline is 3. The description adds extra semantics for the id parameter (present vs omit meaning) and the conditional requirement on institution for creation, going beyond what the schema states.

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 ('Add or update an education entry (upsert)') and clearly distinguishes the two modes (create vs update) based on id presence. The resource is unambiguous, making it easy to tell apart from siblings like save_work_experience even though it doesn't name them.

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?

Provides explicit guidance on when to create (omit id) vs update (pass id from get_profile), and instructs to check get_profile first to avoid duplicates. It doesn't explicitly contrast with sibling tools, but the resource-specific nature makes the intended use clear.

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

All remoet-mcp 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