Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

apk_teardown_diff

Compare two completed APK teardown jobs to identify changes in permissions, signing, SDKs, and app size across versions.

Instructions

Diff two completed apk-teardown jobs. Compares two already-completed jobs -- typically two versions of the same app -- and returns what changed (permissions, signing, SDKs, size, and more).

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_id_a": "<job_id_a>",
      "job_id_b": "<job_id_b>"
    },
    "name": "apk_teardown_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_id_aYesFirst completed job ID; copy data.job_id returned by POST /apk-teardown/jobs
job_id_bYesSecond completed job ID; copy data.job_id returned by another POST /apk-teardown/jobs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.17.16
    • changedInput schema / properties / job_id_a / description
      Previous value: -"First job ID"New value: +"First completed job ID; copy data.job_id returned by POST /apk-teardown/jobs"
    • changedInput schema / properties / job_id_b / description
      Previous value: -"Second job ID"New value: +"Second completed job ID; copy data.job_id returned by another POST /apk-teardown/jobs"
  2. Addedv1.16.2

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden; it does disclose the key precondition that both jobs must be completed and lists what the comparison surfaces (permissions, signing, SDKs, size). It doesn't say what happens if a job is incomplete or whether results are cached, but the core behavioral constraint is disclosed.

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 short sentences, front-loaded with the action and then the returned fields. The second sentence slightly restates the first ('Diff two completed jobs' / 'Compares two already-completed jobs'), a minor redundancy.

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 two-parameter read/comparison tool with full schema coverage and no output schema, the description covers the prerequisite (completed jobs), the typical use case, and the shape of the results. Only edge-case behavior (incomplete jobs, error on mismatch) is unaddressed.

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?

Schema coverage is 100% and both parameters are documented in the schema (including where to get the job_id). The description adds only the typical relationship between the two IDs (two versions of the same app), which is a mild value-add over the schema.

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 (diff/compare) and resource (two completed apk-teardown jobs), and names which attributes are compared (permissions, signing, SDKs, size). It is clear what it does, though it never names the closest sibling apk_teardown_compare_ownership to distinguish the two.

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

Usage Guidelines4/5

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

Gives a concrete usage context: both jobs must be *already completed*, and the typical case is two versions of the same app. It does not state exclusions or point at alternatives such as apk_teardown_job_status for pending jobs, so guidance is good but not exhaustive.

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