Skip to main content
Glama

Import notes

import_notes

Add notes to a knowledge graph so they are processed into facts in the background; include a space_id to store them as a study file for that space.

Instructions

Add notes to a knowledge graph. godspeed turns them into facts in the background; that work arrives through wait_for_work. Returns right away. With space_id the notes become a study file of that space (to add a file from disk, use add_space_file).

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": {
      "name": "<name>",
      "text": "<text>"
    },
    "name": "import_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA file-like name for the notes, e.g. "biology-ch3.md". In a space, re-importing the same name replaces that file and rebuilds its facts; in No space it is processed again and adds to that import.
textYesThe notes.
space_idNoThe space id from list_spaces, or "none" for lessons without a space (the default).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false and idempotentHint=false but say nothing about timing, so the description's disclosure that "godspeed turns them into facts in the background" and "Returns right away" is genuine added value that prevents an agent from expecting immediate facts. The space-scoped overwrite behavior is only covered in the schema's name parameter, not the description, which keeps it from a 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?

Four short sentences, front-loaded with the action and the async consequence before the space_id branch and the parenthetical alternative. The parenthetical sits mid-sentence but carries a real disambiguation, so nothing is wasted.

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?

With no output schema and a mutation tool, the description correctly covers the two things an agent needs: that the call returns immediately and where the real work surfaces (wait_for_work). It does not say what the immediate return value is, which is a small residual gap for a create-style call.

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%, so the baseline is 3, and the description goes beyond it by explaining the semantic effect of space_id (notes become a study file of that space) rather than just restating the field. That effect is not obvious from the schema's terse "space id from list_spaces" wording.

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?

The description opens with a specific verb and resource ("Add notes to a knowledge graph") and immediately scopes it against two siblings: background fact extraction arrives via wait_for_work, and disk files belong to add_space_file. An agent can distinguish it from add_space_file, wait_for_work, and remember without opening a schema.

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?

It gives explicit routing for the closest confusable case ("to add a file from disk, use add_space_file") and explains the async workflow so the agent knows to poll wait_for_work afterward. It stops short of stating when to choose this over remember/save_rule, which are also graph-writing siblings.

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