compose-bridge

by TechsOneAi

Overview Schema Source Related Servers Discussions Admin

Python

Local

This server has been deprecated

Rebranded to ComposeLint AI. Repository has been moved to TechsOneAi/ComposeLintAI.

get_gradle_status

Read-onlyIdempotent

Poll a background Gradle build job to check its status and result after starting it with run_gradle_build; use only when a job ID exists.

Instructions

Check the status and result of a Gradle build job.

When to use:
- Call to poll background Gradle build status returned by run_gradle_build.

When NOT to use:
- Do not use if no Gradle job was started.

Side effects:
- None (strictly read-only job status query).


Args:
    job_id: ID returned by run_gradle_build.
    
Returns:
    JSON with {job_id, status: 'queued'|'running'|'completed'|'failed', result: {...}}.

Input Schema

Name	Required	Description	Default
`job_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.5Oct 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/destructive/idempotent hints, so the 'strictly read-only' line is mostly redundant. The description nonetheless adds real behavioral value the annotations cannot: that this is a polling endpoint, that job_id is a background handle, and the status state machine (queued|running|completed|failed).

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?

Front-loaded purpose followed by labeled sections, which is easy to scan. A few lines (the 'Side effects: None' note, the Args/Returns headers) repeat structured data or boilerplate and could be trimmed without losing meaning.

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

Completeness5/5

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

For a single-parameter read tool this covers everything an agent needs: purpose, invocation condition, exclusion, argument provenance, and the shape and enumeration of the response. No output schema is required to disambiguate the return value.

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 0% — job_id is an undocumented string — so the description carries the burden, and it does: it identifies job_id as the ID returned by run_gradle_build, which tells the agent where to obtain the value. The expected format of the ID itself is still unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Check the status and result of a Gradle build job') and ties it to the sibling that produces the job, so an agent can separate it from run_gradle_build or list_allowed_gradle_tasks without opening the schema.

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

Usage Guidelines5/5

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

Explicit 'When to use' (polling background status returned by run_gradle_build) and 'When NOT to use' (no Gradle job started) sections, naming the related tool directly. Nothing is left to inference.

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