Skip to main content
Glama

signafAIde sandbox claim link

signafaide_claim_link

The link the human opens to claim this project's free sandbox and keep its records, what claiming gives and how long an unclaimed sandbox has left. Show it to the user; do not open it yourself.

Instructions

The link the human opens to claim this project's free sandbox and keep its records, what claiming gives and how long an unclaimed sandbox has left. Show it to the user; do not open it yourself.

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_claim_link"
  }
}

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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations to lean on, the description carries the burden and does reasonably well: it discloses that the response includes not just a link but also what claiming grants and how much time an unclaimed sandbox has left, and it warns against the agent fetching the URL itself. It does not say whether the tool is side-effect free or what happens when the sandbox is already claimed or expired.

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?

It is a single compact sentence-pair with zero filler, and the directive to show rather than open the link comes last where it is easy to act on. The opening noun-phrase construction ("The link ... what claiming gives and how long ...") reads as a stacked fragment and takes a second pass to parse cleanly.

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

Completeness4/5

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

For a low-complexity, one-optional-parameter tool with no output schema and no annotations, the definition covers what is returned and how the caller should handle it. The main residual gap is the missing call-trigger and error/edge-case behavior for an already-claimed or expired sandbox.

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 single optional `directory` parameter has 100% schema description coverage, so the schema already defines its meaning and default. The description adds no extra semantics about directory scoping, which is acceptable at this coverage level but is the baseline rather than added value.

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?

The description identifies the resource precisely — the claim link for this project's free sandbox — and adds what claiming yields and the remaining time on an unclaimed sandbox. It is phrased as a noun phrase rather than a verb+resource statement, and it does not explicitly contrast itself with siblings like signafaide_status or signafaide_init, though the purpose is still unmistakable.

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?

It gives a handling directive ("Show it to the user; do not open it yourself"), which is genuinely useful, but it never states the trigger condition for calling it — e.g., when a sandbox is unclaimed or nearing expiry — nor any alternative to use instead. Usage is implied by the subject matter rather than spelled out.

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