Skip to main content
Glama
Obsideo MCP server

Obsideo MCP server

by Regan-Milne

Create an instant trial account (no email)

trial
Destructive

Creates a free Obsideo account without email or manual identity checks, saving production credentials locally to enable cloud file storage.

Instructions

Create a free Obsideo account with no email and no human in the loop: a small proof-of-work and a ~10 second wait in place of identity. Returns a real account on the production network (100 MB, about 7 days, RF=3 replication, continuous possession proofs) and saves credentials locally. You usually do NOT need to call this: the first put/get/ls/usage auto-creates a trial if no account is configured. Call it to provision explicitly. To keep data beyond the trial, claim it with an email via signup_start (same account and data, quota rises to 8 GB free with no card and no expiry; 16 GB after the account holder answers eight questions in the Drive web app). Takes about 15 to 30 seconds (proof of work plus a 10 second issuance window); progress is reported while it runs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "trial"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceNoWhere you found Obsideo (defaults to 'mcp')
replaceNoOnly if the human explicitly wants a fresh, separate account: replace the account already configured on this machine. Without it, this tool refuses when an account exists.

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?

Goes well beyond the annotations: discloses the proof-of-work gate, the ~10 second issuance window, 15-30 second total runtime with progress reporting, concrete account limits (100 MB, ~7 days, RF=3, continuous possession proofs), production-network placement, and the side effect of saving credentials locally. This is consistent with destructiveHint=true, since replace=true overwrites an existing configured account.

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?

Front-loaded with the action and the key "you usually do NOT need to call this" caveat, which is exactly the right ordering. It is somewhat dense in the final sentence (the eight-questions/16 GB detail is tangential), but every clause carries real information.

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 zero-required-parameter provisioning tool with no output schema, it covers everything an agent needs: latency, progress feedback, what is created, where credentials go, trial limits, and the upgrade path. Nothing material is missing.

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 100%, so both `source` and `replace` are already documented in structured form, and the description adds no syntax or format detail for either. The mention that the tool "refuses when an account exists" is already in the `replace` schema text, so the description does not meaningfully extend parameter meaning.

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?

States a specific verb and resource ("Create a free Obsideo account") plus the defining constraint ("no email and no human in the loop"), which cleanly separates it from signup_start, signup_verify, and verify among the siblings.

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

Usage Guidelines5/5

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

Explicitly says when NOT to call it ("You usually do NOT need to call this: the first put/get/ls/usage auto-creates a trial if no account is configured") and names the alternative path for persistence ("claim it with an email via signup_start"). Both the default behavior and the explicit-provisioning case are covered.

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