Skip to main content
Glama

remoet

by dev.remoet.api
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. Saving without an id always creates a new entry.

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.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false; the description usefully reinforces non-idempotency ('Saving without an id always creates a new entry') and partial-update semantics ('changing only the fields you send'). It stops short of describing what is returned or how duplicates are handled, so it is not a full 5.

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?

Front-loaded with the core upsert behavior and otherwise tight, but the final sentence ('Saving without an id always creates a new entry') repeats the first sentence's create condition, which is minor redundancy.

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 mutation tool with no output schema and annotations covering the safety profile, the description covers the create/update contract and required field adequately. It does not state what the call returns or how the saved entry is identified, a small remaining 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 100%, so the schema already documents every parameter, including the id create/update semantics that the description restates. The description adds no field-level meaning beyond the schema, so the baseline 3 is appropriate.

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 (add/update, upsert) and a specific resource (education entry), and immediately differentiates from siblings like save_work_experience and save_project. The agent can identify the tool's job without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit create-vs-update branching (omit id to create, pass id from get_profile to update), states the create prerequisite (institution required), and adds when/what to ask the user (degrees, bootcamps, certifications; confirm approximate dates instead of guessing). This is genuinely actionable routing guidance.

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

All remoet toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources