Skip to main content
Glama

aw.artifact.verify

Read-only

Re-read authenticated chunks and hash an actual current-session artifact; return metadata, never audio bytes.

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": {
      "session": "<session>",
      "artifactId": "<artifactId>"
    },
    "name": "aw.artifact.verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionYesPrivate short-lived session capability returned by aw.session.open. Never publish or log it.
artifactIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: it re-reads chunks (implying I/O cost over a live session) and deliberately returns metadata only, never audio bytes, which tells the agent not to expect payload data. It stops short of saying whether verification can fail or what a mismatch looks like.

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 dense sentence with the key constraint ('never audio bytes') placed last for emphasis. No filler, though the phrasing 'hash an actual current-session artifact' is slightly compressed and could be clearer about what is being hashed.

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?

The tool is simple (two required params, no nesting), and annotations plus the description cover the safety and output-shape basics. However, with no output schema, 'return metadata' is left undefined — the agent cannot tell what fields come back or how a verification failure surfaces. That gap keeps it at minimum-viable.

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?

Schema coverage is 50%: session is documented in the schema as a private short-lived capability that must not be logged, while artifactId carries only a pattern and no prose. The description adds nothing about either parameter, so it does not compensate for the artifactId gap. Baseline 3 applies.

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 action on a specific resource: re-reads authenticated chunks, hashes the current-session artifact, and returns metadata rather than bytes. That output-shape contrast implicitly distinguishes it from aw.artifact.read_chunk, though the sibling is never named. Purpose is clear without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied: 'verify' connotes an integrity check, and 'never audio bytes' hints you should use this instead of a byte-fetching read when you only need confirmation. There is no explicit when-to-use, no precondition, and no named alternative, so the agent must infer routing from the sibling list.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources