Skip to main content
Glama

gradle-get-details

Retrieve detailed build or test output from Android development projects by specifying an ID. Access logs, errors, tasks, or complete results with configurable truncation and summary options.

Instructions

Fetch full output for a previous build/test by ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
detailTypeNo
maxCharsNoTruncate to N chars
summaryOnlyNoReturn compact summary payload for logs/tasks/all detail types (ignored for errors)
previewCharsNoFor summaryOnly with detailType logs/all: preview length in characters (default: 400)

Implementation Reference

  • The main handler function for the gradle-get-details tool, which retrieves data from the cache and formats it based on the requested detailType.
    export async function handleGradleGetDetailsTool(
      input: GradleGetDetailsInput,
      context: ServerContext
    ): Promise<Record<string, unknown>> {
      const { fullOutput, result, operation } = getCacheEntry(input, context);
      const previewChars = input.previewChars ?? 400;
    
      switch (input.detailType) {
        case "logs":
          return buildLogsResponse(input, fullOutput, operation, previewChars);
        case "errors":
          return buildErrorsResponse(input, fullOutput, operation);
        case "tasks":
          return buildTasksResponse(input, fullOutput, operation);
    
        case "all":
        default:
          return buildAllResponse(input, fullOutput, result, operation, previewChars);
      }
    }
  • Zod input schema definition for the gradle-get-details tool.
    export const gradleGetDetailsInputSchema = z.object({
      id: z.string(),
      detailType: z.enum(["logs", "errors", "tasks", "all"]).optional().default("all"),
      maxChars: z.number().min(1).optional(),
      summaryOnly: z.boolean().optional(),
      previewChars: z.number().min(1).optional(),
    });
    
    export type GradleGetDetailsInput = z.infer<typeof gradleGetDetailsInputSchema>;
  • The definition object for the gradle-get-details tool, used for registration.
    export const gradleGetDetailsToolDefinition = {
      name: "gradle-get-details",
      description: "Fetch full output for a previous build/test by ID.",
      inputSchema: {
        type: "object",
        properties: {
          id: { type: "string" },
          detailType: {
            type: "string",
            enum: ["logs", "errors", "tasks", "all"],
          },
          maxChars: {
            type: "number",
            description: "Truncate to N chars",
          },
          summaryOnly: {
            type: "boolean",
            description: "Return compact summary payload for logs/tasks/all detail types (ignored for errors)",
          },
          previewChars: {
            type: "number",
            description: "For summaryOnly with detailType logs/all: preview length in characters (default: 400)",
          },
        },
        required: ["id"],
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
    };
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 but offers minimal detail. It does not clarify the output format, error handling (e.g., invalid ID), whether the operation is idempotent, or explain the truncation behavior implied by maxChars/previewChars parameters. 'Fetch' implies read-only, but this is not explicitly stated.

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?

The single-sentence description is front-loaded with the action verb and contains no redundant or wasteful text. However, given the tool's 5 parameters and lack of output schema, the extreme brevity arguably underserves the complexity rather than demonstrating efficient conciseness.

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

Completeness2/5

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

For a tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It fails to describe the output structure, does not explain that the ID comes from previous gradle-build/test executions, and omits guidance on selecting between detailTypes (logs, errors, tasks, all) which is critical for effective 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?

With 60% schema description coverage, the baseline is 3. The description mentions 'by ID' referencing the id parameter, and 'full output' hinting at detailType options, but does not compensate for the lack of schema descriptions on the 'id' (what ID format?) and 'detailType' (what are logs vs tasks vs errors?) parameters. It adds marginal context but leaves key parameters undocumented.

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 verb (Fetch), resource (full output for a previous build/test), and scope (by ID). It effectively distinguishes this tool from siblings like 'gradle-build' and 'gradle-test' (which execute new runs) by specifying 'previous' build/test, though it could be more specific about what 'full output' encompasses (logs, errors, tasks).

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 explicit guidance on when to use this tool versus alternatives like 'gradle-list' or 'gradle-build'. While 'previous' implies this retrieves historical data, it fails to state that this should be used after a build/test completes to retrieve results, or when to prefer specific detailTypes over others.

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/thecombatwombat/replicant-mcp'

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