Skip to main content
Glama

add_note

Attach an interpretive note to an archaeological unit and keep it in the edit history for traceable context and later review.

Instructions

Attach an interpretive note to a unit (kept in the edit history).

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": {
      "unit": "<unit>",
      "note": "<note>"
    },
    "name": "add_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
siteNo
unitYes
authorNoagent

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose one useful trait beyond the schema — the note is retained in the edit history, implying persistence and visibility to other users — but says nothing about permissions, whether notes are editable/removable, or duplicate handling.

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?

A single short sentence with the key operation front-loaded and no filler. It is efficient, though the brevity is partly the cause of the coverage gaps rather than a virtue in itself.

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

Completeness3/5

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

Because an output schema exists, return values need not be explained, and the tool is structurally simple. Still, a mutation tool with zero annotations and two entirely undocumented parameters should say more about author defaults and site scoping to be reliably invocable.

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

Parameters2/5

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

Schema description coverage is 0% across 4 parameters. The description only implicitly covers two of them (the note text and the target unit); `site` and `author` (with its "agent" default) are completely undocumented in both schema and description, so meaning is not added beyond bare types.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Attach an interpretive note to a unit"), which distinguishes it from read-oriented siblings like "history" or "provenance". It doesn't explicitly name a sibling alternative, but the action is unambiguous.

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

Usage Guidelines2/5

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

There is no explicit guidance on when this tool should be used instead of alternatives such as "history" or "provenance", and no prerequisites or exclusions are stated. The word "interpretive" hints at intent but leaves the agent to infer the triggering condition.

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