Skip to main content
Glama

get_any

Retrieve archived snapshots, results, or tags by their unique identifier to access specific archived content from ArchiveBox.

Instructions

Get a specific Snapshot, ArchiveResult, or Tag by abid.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
abidYesThe abid of the Snapshot, ArchiveResult, or Tag

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP tool handler for 'get_any': decorated with @mcp.tool, defines parameters with pydantic Field for schema, creates Api client and calls client.get_any to fetch data by abid.
    @mcp.tool(
        exclude_args=[
            "archivebox_url",
            "username",
            "password",
            "token",
            "api_key",
            "verify",
        ],
        tags={"core"},
    )
    def get_any(
        abid: str = Field(
            description="The abid of the Snapshot, ArchiveResult, or Tag",
        ),
        archivebox_url: str = Field(
            default=os.environ.get("ARCHIVEBOX_URL", None),
            description="The URL of the ArchiveBox instance",
        ),
        username: Optional[str] = Field(
            default=os.environ.get("ARCHIVEBOX_USERNAME", None),
            description="Username for authentication",
        ),
        password: Optional[str] = Field(
            default=os.environ.get("ARCHIVEBOX_PASSWORD", None),
            description="Password for authentication",
        ),
        token: Optional[str] = Field(
            default=os.environ.get("ARCHIVEBOX_TOKEN", None),
            description="Bearer token for authentication",
        ),
        api_key: Optional[str] = Field(
            default=os.environ.get("ARCHIVEBOX_API_KEY", None),
            description="API key for authentication",
        ),
        verify: Optional[bool] = Field(
            default=to_boolean(os.environ.get("ARCHIVEBOX_VERIFY", "True")),
            description="Whether to verify SSL certificates",
        ),
    ) -> dict:
        """
        Get a specific Snapshot, ArchiveResult, or Tag by abid.
        """
        client = Api(
            url=archivebox_url,
            username=username,
            password=password,
            token=token,
            api_key=api_key,
            verify=verify,
        )
        response = client.get_any(abid=abid)
        return response.json()
  • Helper method in Api class: performs HTTP GET request to ArchiveBox API endpoint /api/v1/core/any/{abid} to retrieve the resource.
    def get_any(self, abid: str) -> requests.Response:
        """
        Get a specific Snapshot, ArchiveResult, or Tag by abid
    
        Args:
            abid: The abid of the Snapshot, ArchiveResult, or Tag.
    
        Returns:
            Response: The response object from the GET request.
    
        Raises:
            ParameterError: If the provided parameters are invalid.
        """
        try:
            response = self._session.get(
                url=f"{self.url}/api/v1/core/any/{abid}",
                headers=self.headers,
                verify=self.verify,
            )
        except ValidationError as e:
            raise ParameterError(f"Invalid parameters: {e.errors()}")
        return response
  • Registration of the 'get_any' tool using @mcp.tool decorator, excluding auth args and tagging as core.
    @mcp.tool(
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves a resource by abid, implying a read-only operation, but doesn't describe what happens if the abid is invalid, whether authentication is required, or any rate limits. This leaves significant gaps in understanding the tool's behavior beyond its basic function.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence that efficiently conveys the tool's purpose without any unnecessary words. It is front-loaded and appropriately sized for its function, making it easy to understand at a glance.

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?

Given the tool's simplicity (one parameter, read-like operation) and the presence of an output schema, the description is adequate but incomplete. It lacks behavioral details (e.g., error handling, auth needs) that are not covered by annotations or schema, and it doesn't clarify the relationship with sibling tools, leaving room for confusion in usage.

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 schema description coverage is 100%, with the parameter 'abid' clearly documented in the schema as the identifier for Snapshot, ArchiveResult, or Tag. The description adds minimal value by restating that abid is used to get these resources, but doesn't provide additional context like format examples or constraints beyond what the schema already covers.

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 clearly states the tool's purpose: retrieving a specific resource (Snapshot, ArchiveResult, or Tag) by its identifier (abid). It uses a specific verb ('Get') and identifies the target resources, though it doesn't explicitly differentiate from similar sibling tools like get_snapshot, get_archiveresults, or get_tag, which appear to be more specialized versions.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention why one would choose get_any over the more specific sibling tools (e.g., get_snapshot for snapshots only), nor does it specify any prerequisites or exclusions for usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Knuckles-Team/archivebox-api'

If you have feedback or need assistance with the MCP directory API, please join our Discord server