Skip to main content
Glama
anchor-notes-mcp

anchor-notes-mcp

by NatanaelJose

list_attachments

Read-only

List the images and audio attached to a specific Anchor note using its note ID, so you can review or manage the note's media files.

Instructions

List a note's attachments (images and audio).

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": {
      "noteId": "<noteId>"
    },
    "name": "list_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteIdYes

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?

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds the useful scope detail that only image and audio attachments are returned, but says nothing about ordering, empty results, or whether trashed notes are included.

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?

One short sentence, front-loaded with the verb and resource, with no filler. Its brevity is close to under-specification rather than verbosity, but there is no wasted wording.

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?

For a simple read-only single-parameter list tool with annotations covering safety, the description is minimally adequate: it identifies the resource and the attachment types. It is incomplete on the one parameter it requires and on whether results can be empty or paginated.

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% on the single required parameter noteId, so the schema supplies no meaning on its own, and the description never explains that noteId identifies which note's attachments are listed or what format it takes. The description therefore fails to compensate for the coverage gap.

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?

States a specific verb and resource ("List a note's attachments") and narrows the scope to images and audio, which separates it from singular siblings like get_attachment and mutation siblings like add_attachment or delete_attachment. It stops short of naming any alternative explicitly, so differentiation is implicit rather than stated.

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?

The description never says when to use this tool versus get_attachment (fetch a single attachment) or delete_attachment, nor does it mention prerequisites such as needing the note to exist. Usage is only inferable from the verb "List".

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