Skip to main content
Glama
Obsideo MCP server

Obsideo MCP server

by Regan-Milne

Prove an object is really stored (client-side)

verify
Read-only

Verify that a stored object is still held by the network without downloading it. Challenges each provider and compares answers against a merkle root, reporting how many proved possession.

Instructions

Independently verify that the network still holds an object, without downloading it. Challenges each provider directly and compares every answer, on this machine, against a merkle root. For objects stored through this server, that root is the one this machine recorded at upload time, if the local record still has it. Pass local_path (your copy of the stored file) to compare against a root computed from that file instead. If neither is available, it falls back to the coordinator's recorded root and says so. The coordinator chooses which providers to ask, where to reach them, and the public keys their signatures are checked against, and issues the challenge tokens. Each provider is challenged on one randomly chosen chunk. Returns how many providers proved possession right now, how many of those answers were signed, and whether any returned bad data.

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": {
      "key": "<key>"
    },
    "name": "verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesObject key to verify, e.g. backups/db-2026-08-13.sql.zst
local_pathNoYour local copy of the stored bytes (optional; only needed for objects this server did not upload)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.2

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses the full verification behavior: challenges are issued directly to providers, responses are compared locally against a merkle root, and the coordinator controls provider selection, endpoints, public keys, and challenge tokens. It also explains the random chunk selection and what the return values summarize.

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 description is front-loaded and every sentence contributes relevant behavioral detail, including trust assumptions and fallback behavior. It is somewhat long, but with no obvious waste given the complexity of the verification process.

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

Completeness5/5

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

For a complex network-verification tool with no output schema, the description covers the verification mechanism, trust model, fallback behavior, and the shape of the return summary. An agent should have enough information to decide when and how to call it correctly.

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 the schema already documents both parameters. The description adds meaningful semantics for local_path by explaining that it is used to compute an alternative root from the caller's copy of the stored bytes, and clarifies the fallback when neither local root nor local_path is available.

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 states a specific verb and resource: independently verify that the network still holds an object, without downloading it. It clearly distinguishes verification from retrieval tools like get and describes the core mechanism of challenging providers and comparing answers against a merkle root.

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

Usage Guidelines4/5

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

The description explains when to supply local_path versus relying on the server-recorded root, and what happens if neither is available. It does not explicitly name alternative sibling tools or when-not to use this tool, but the usage context is clear.

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