Skip to main content
Glama

read_assets

Read-only

Retrieve files attached to a LeafWiki page by id or path, including URLs to embed or link them.

Instructions

Files attached to a page, with the URL to embed or link them.

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": {
      "page": "<page>"
    },
    "name": "read_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesPage id or path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally. The description's one real contribution is disclosing the shape of the result — assets come back with URLs ready to embed or link — which is genuinely useful. It says nothing about pagination, ordering, or behavior when a page has no attachments.

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 clause with zero filler, and the return-value detail is packed in efficiently. The only cost is that it is a sentence fragment rather than a statement of action, which slightly reduces front-loaded clarity.

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 one-parameter read tool with annotations and no output schema, the description covers enough to call it correctly: which page to pass and what comes back. It stops short of telling the agent when to reach for this rather than another read tool, which is the remaining gap given how many read siblings exist.

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?

With one parameter at 100% schema coverage, the schema already defines 'page' as an id or path. The description only echoes 'attached to a page' and adds no format, resolution, or edge-case meaning beyond the schema, so the baseline 3 applies.

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

Purpose3/5

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

The description names the resource (files attached to a page) and its return value (an embeddable/linkable URL), which lets an agent infer it lists page assets. But it is a bare noun phrase with no verb, so what the tool actually does — list, fetch, or resolve asset URLs — is left implicit, and it does not distinguish itself from read_links or read_page by anything other than the word 'Files'.

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 when-to-use guidance at all: no statement of preconditions (e.g. the page must exist), no indication of how it relates to read_page or read_links, and no pointer to the delete_asset sibling for the destructive counterpart. The agent must infer the calling context entirely from the tool name.

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