remoet

Official

by remoet-labs

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Update Education

update_education

Idempotent

Update an existing education entry by ID. Provide only the fields you want to change; omitted fields remain as-is.

Instructions

Update an existing education entry. Only provide the fields you want to change — omitted fields are left as-is. Use get_education first to find the ID. Prefer this over delete + recreate — it preserves the entry ID.

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": {
      "id": "<id>"
    },
    "name": "update_education"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The ID of the education entry to update
`institution`	No	Institution name
`institutionUrl`	No	Institution website URL
`studyLevel`	No	Level of study: HIGH_SCHOOL, ASSOCIATE, BACHELOR, MASTER, DOCTORATE, BOOTCAMP, or OTHER
`fieldOfStudy`	No	Field of study
`startDate`	No	Start date (ISO 8601)
`endDate`	No	End date (ISO 8601)
`isCurrent`	No	Whether you are currently studying here
`description`	No	Description of studies, achievements, etc.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 28, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already indicate idempotentHint=true and destructiveHint=false. Description adds behavioral detail that omitted fields are left as-is, which is beyond annotations. No contradiction.

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 sentences with no wasted words. Front-loaded with purpose, then guidelines. Highly concise and structured.

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?

Given no output schema, description covers usage flow and behavioral expectations. Slightly missing return value information, but overall complete for a simple update tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions. The description adds critical semantics that only provided fields are changed, which is not captured in the schema alone.

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?

Description clearly states 'Update an existing education entry' with specific verb and resource. It distinguishes from siblings like create_education and delete_education by advising to use get_education first and preferring update over delete+recreate.

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?

Explicitly says to use get_education to find the ID first and prefers this over delete+recreate, providing clear context on when to use and alternatives.

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