Skip to main content
Glama

Create an external signafAIde sandbox (ask the user first)

signafaide_init

Creates an external sandbox project on the signafAIde service (or the SIGNAFAIDE_URL witness), saves its API key to .env and returns the claim link, what claiming gives and when an unclaimed sandbox is deleted.

Instructions

Creates an external sandbox project on the signafAIde service (or the SIGNAFAIDE_URL witness), saves its API key to .env and returns the claim link, what claiming gives and when an unclaimed sandbox is deleted. From then on record hashes (never content) are sent there, and records written earlier ship with their original times. This is an external side effect: ask the user and call it only after they agree. Without it, records stay local and still verify. Creating a sandbox means the user agrees to the signafAIde Terms and Privacy notice (/legal/terms and /legal/privacy, where is SIGNAFAIDE_URL or the signafAIde service): show them both links when you ask, and pass on the notice this tool returns. It creates nothing unless confirm_user_agreed is true and user_words holds what the user wrote when they agreed.

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": "signafaide_init"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryNoPath of the project to work on: the folder the MCP server was started in, or one below it. Default: that folder.
user_wordsNoThe user's own words when they agreed, quoted from the conversation (for example "yes, create the sandbox").
confirm_user_agreedNoSet to true only after the user, in this conversation, agreed to create the sandbox and to the Terms and Privacy notice. Never set it on your own judgement.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses the external side effect, .env mutation, the returned claim link and notice, when an unclaimed sandbox is deleted, that hashes (never content) are sent, and that earlier records ship with original timestamps. Consent requirements and the 'creates nothing unless' guard are also stated.

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?

Purpose and consent requirement are front-loaded and every clause is substantive, but sentences are long and multiply nested parentheticals (SIGNAFAIDE_URL, legal paths, notice pass-through) make it denser than needed. Slight tightening would improve scanability without losing 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 mutation tool with no annotations and no output schema, the description supplies what is returned, what is written, what gets deleted and when, and the consent prerequisites. An agent has enough to decide, ask, and invoke 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 baseline is 3; the description adds real meaning by explaining the confirm_user_agreed/user_words contract as a consent gate rather than a formality. The directory parameter is left to the schema, which is acceptable given full coverage.

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 ('Creates an external sandbox project on the signafAIde service') and enumerates its concrete effects: saving an API key to .env, returning the claim link, and shipping record hashes externally. The scope difference from local-only behavior ('Without it, records stay local and still verify') makes it distinguishable from setup/status/claim_link 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 tells the agent when to call it (only after the user agrees, with both legal links shown) and when not to (records stay local and still verify without it). It also names the gating condition that suppresses creation, which is stronger guidance than most definitions provide.

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