Skip to main content
Glama
Sign In
ArchiveBox API

ArchiveBox API

by Knuckles-Team
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get current machine

archivebox_get_current_machine
Read-onlyIdempotent

Retrieves details about the machine hosting the ArchiveBox API, helping identify the current server instance.

Instructions

GET /api/v1/machine/machine/current

Read the machine serving this API.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.6.0

TDQS

B3.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is fully covered elsewhere. The description's 'GET ...' line merely restates that this is a read, and 'Read the machine serving this API' adds no behavioral detail such as what the machine record contains or whether a machine must be registered first.

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?

Two lines, front-loaded with the resource identification, with no filler sentences. The raw 'GET /api/v1/machine/machine/current' line is somewhat redundant for an MCP caller and the doubled 'machine/machine' path segment reads as noise, but the overall size is appropriate.

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

Completeness3/5

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

For a parameterless read with full annotation coverage and no output schema, little is required, and the description establishes what is returned at a high level. It stops short of describing the shape of the machine record (identity, name, timestamp fields), which is the one thing an agent cannot infer from structured fields here.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool is 4. The text correctly implies the identity of the returned machine is derived implicitly from the API host rather than from any input.

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 gives a specific verb ('Read') and resource ('the machine serving this API'), which is meaningfully distinct from its siblings. It does not, however, explicitly contrast with archivebox_get_machine or archivebox_get_machines, so an agent must infer the difference from the word 'current'.

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?

Usage is only implied: the phrase 'serving this API' hints that this is the local/self machine rather than an arbitrary one, but the description never states when to call this instead of archivebox_get_machines or archivebox_get_machine. No prerequisites, exclusions, or alternative routing are provided.

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

Deploy Server

Other Tools