Skip to main content
Glama

describe_item

Writes a searchable name and note for one archive item, turning what is visible in the image into plain Markdown saved beside the file.

Instructions

Write the name and note for one item in the archive.

This is the tool that earns the server its keep. Describing an archive by hand is the slow, valuable work that makes everything else findable — search by meaning has nothing to rank without it, and list_folders will tell you exactly which folders are thin.

Look at the image with view_inspo FIRST, then describe what is actually there. A guess from the filename is worse than no description: it will be searched, believed, and never checked.

The NAME is one line — what this is, in the words somebody would look for. It becomes the item's name everywhere in the app. The NOTE is the longer thought: why it was kept, what to steal from it. Either can be left out to keep what is already written; passing an empty string clears it.

Writes to the _manifest.md file beside the image, in plain Markdown, so the words outlive this app.

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": {
      "path": "<path>"
    },
    "name": "describe_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOne line. What this is. Omit to leave the existing one.
noteNoThe longer thought. Omit to leave the existing one.
pathYesThe item, as search_inspo reports it: "@<root>/<folder>/<file>".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and mostly succeeds: it discloses the write target (_manifest.md beside the image, plain Markdown), the field-level merge semantics (omit to preserve, empty string to clear), and the broad blast radius of the name. It does not cover failure modes, path validation, or whether a missing item is created, which keeps it short of 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?

The core action and the view_inspo prerequisite are front-loaded and the paragraphs are logically ordered (purpose, guidance, field semantics, storage). Some motivational phrasing ('earns the server its keep', 'the slow, valuable work') is padding that could be trimmed without losing instruction.

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 3-parameter write tool with no output schema and no annotations, the description covers what changes, where it is stored, and how omitted fields behave. It stops short of describing the response or error behavior, but nothing critical for invoking it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds genuine meaning beyond the schema: the NAME is framed as search-facing vocabulary and the NOTE as rationale ('why it was kept, what to steal from it'), and it states that an empty string clears a field, which the schema does not. The path parameter's format is left entirely to the schema.

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 first sentence states a specific verb and resource: writing the name and note for one item in the archive. Later sentences pin down the effect ('It becomes the item's name everywhere in the app') and the storage target, so it is clearly distinguishable from siblings like rename_file or move_file.

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?

It gives an explicit ordering constraint ('Look at the image with view_inspo FIRST'), an explicit anti-pattern ('A guess from the filename is worse than no description'), and a complementary sibling for prioritization (list_folders for thin folders). This is real when-and-how guidance, not just context.

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