Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apk_teardown_timeline

Build an APK version timeline from two or more completed teardown jobs for the same app, comparing consecutive versions and returning pairwise diffs sorted by version code.

Instructions

Build a version timeline across 2+ apk-teardown jobs. Compares 2+ completed jobs the caller asserts are versions of the same app and returns the consecutive pairwise diff for each version transition, sorted by version code.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "job_ids": "<job_ids>"
    },
    "name": "apk_teardown_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idsYesComma-separated list of 2+ completed job IDs copied from data.job_id values returned by POST /apk-teardown/jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.16
    • changedInput schema / properties / job_ids / description
      Previous value: -"Comma-separated list of 2+ completed job ids, any order"New value: +"Comma-separated list of 2+ completed job IDs copied from data.job_id values returned by POST /apk-teardown/jobs"
  2. Addedv1.16.2

TDQS

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses output shape (consecutive pairwise diffs per transition) and ordering (by version code), but says nothing about failure behavior for non-completed jobs, whether it is purely read-only, or cost/latency for large job sets.

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?

Two sentences, no filler, with the core action and input constraint front-loaded and return semantics following. Every clause contributes binding information.

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 single-parameter aggregation tool with no annotations and no output schema, the description is close to sufficient: it explains inputs, output structure, and ordering. The remaining gap is edge-case behavior (incomplete or unrelated jobs), which is minor but non-trivial for a tool whose correctness depends on the caller's assertion.

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% and the schema itself explains the comma-separated job ID format and provenance. The description adds semantics beyond that: the IDs must be completed jobs and are asserted by the caller to be versions of one app, which is a correctness constraint the schema does not state.

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?

States a specific verb and resource ('Build a version timeline across 2+ apk-teardown jobs') and describes the comparison scope (2+ completed jobs treated as versions of the same app). It implicitly separates itself from apk_teardown_diff by emphasizing multi-version timelines, but never names the sibling, so differentiation requires inference.

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?

Adds real preconditions: at least two jobs, all completed, and the caller must assert they are versions of the same app. However it never says when to prefer apk_teardown_diff or apk_teardown_job_status, so the agent must reason about sibling choice rather than being routed.

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