Skip to main content
Glama

Handover

by sh.handover
OverviewDiscussionsAdmin

Import an OKF bundle

handover.okf.import

Import Open Knowledge Format files into a new immutable Handover revision. Replaying the same bundle is idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoMerge bundle files with inherited artifacts or replace them.merge
filesYesFiles from an Open Knowledge Format bundle.
handoverIdYesExisting handover that will receive the imported bundle.
expectedRevisionIdNoCurrent revision ID used to prevent conflicting imports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / expectedRevisionId / description
      Added value: +"Current revision ID used to prevent conflicting imports."
    • addedInput schema / properties / files / description
      Added value: +"Files from an Open Knowledge Format bundle."
    • addedInput schema / properties / files / items / properties / content / description
      Added value: +"UTF-8 text, or base64 when encoding is base64."
    • addedInput schema / properties / files / items / properties / encoding / description
      Added value: +"How content is encoded in this request."
    • addedInput schema / properties / files / items / properties / mediaType / description
      Added value: +"IANA media type; inferred from path when omitted."
    • addedInput schema / properties / files / items / properties / path / description
      Added value: +"Relative path of this file inside the OKF bundle."
    • addedInput schema / properties / handoverId / description
      Added value: +"Existing handover that will receive the imported bundle."
    • addedInput schema / properties / mode / description
      Added value: +"Merge bundle files with inherited artifacts or replace them."
  2. First observed

TDQS

B3/5.0
Behavior1/5

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

The description claims 'Replaying the same bundle is idempotent,' but the annotations declare idempotentHint=false. This is a direct contradiction. No additional behavioral context about permissions, error handling, or side effects is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with no unnecessary words. Information is front-loaded and easy to parse.

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

Completeness2/5

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

Although the schema is complete, the tool is a mutation with no output schema and the description omits usage guidance, potential errors, and conflict-handling behavior. The idempotency contradiction further reduces completeness and trustworthiness.

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?

The schema provides 100% coverage with detailed parameter descriptions, so the baseline is 3. The description adds minimal value beyond schema, only linking handoverId to the concept of an immutable revision.

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 description clearly states the verb (Import), the resource (Open Knowledge Format files), and the destination (a new immutable Handover revision). It distinguishes from sibling tools like export_okf and handover.okf.export by focusing on import into Handover.

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?

No guidance is provided on when to use this tool versus alternatives such as import_okf or handover.okf.export. The description lacks any context about prerequisites, exclusions, or typical scenarios.

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

All Handover toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources