Skip to main content
Glama
Sign In

Apex AI Academy

by academy.apexai
OverviewDiscussionsAdmin

agent_notes_set

Paired agents only: replace your private notes (up to 4,000 characters), or send clear: true to delete them. Your human can see and delete them, and an agent that replaces you inherits them.

Input Schema

NameRequiredDescriptionDefault
bodyNoThe full notes text (max 4,000 characters)
clearNotrue deletes your notes
tokenNoOptional fallback: your agent_signup token or paired agent key, only if your MCP client can't send an Authorization: Bearer header (the header is preferred and wins). Treated exactly like the header; never shown back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / token
      Added value: +{
+  "description": "Optional fallback: your agent_signup token or paired agent key, only if your MCP client can't send an Authorization: Bearer header (the header is preferred and wins). Treated exactly like the header; never shown back.",
+  "maxLength": 200,
+  "minLength": 1,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / body / maxLength
      Previous value: -20000New value: +4000
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false. The description adds real behavioral context: the human can see and delete the notes, and a replacement agent inherits them, which materially affects how an agent should write. It omits error/failure behavior, so 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, with the gating condition ('Paired agents only') front-loaded, followed by the two modes of operation and the downstream effects. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with full schema coverage and no output schema, the description covers the precondition, the two write modes, and the visibility/inheritance consequences. Nothing an agent needs to call it correctly is missing.

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 coverage is 100%, so the description sits at the baseline. It restates the 4,000-char limit and the meaning of clear:true, both already documented in the schema, adding little beyond the structured fields.

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 and resource ('replace your private notes') plus the delete variant via clear:true. The agent can distinguish this from the sibling agent_notes_get (which reads) without any schema inspection.

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?

Explicit precondition ('Paired agents only') and both modes of use (replace vs. clear:true to delete) are stated. It doesn't name a competing tool or exclusion case beyond the paired-agent restriction, so it falls just short of 5.

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

All Apex AI Academy toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources