Skip to main content
Glama
thyn-ai

Algenta MCP

Official
by thyn-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

triage_repository

Condense a repository snapshot and issue signals into a ranked evidence bundle of suspect files and symbols, with budget-capped snippets for planner use.

Instructions

Condense one repository snapshot into a bounded workspace evidence bundle for the planner: ranked suspect files and symbols with scored, budget-capped snippets. signals seeds the search — pass issue_text, diagnostics, failing_tests, changed_files, and/or workspace_context. The returned workspace_evidence_bundle_ref is the required input to create_repository_decision_plan; use run_repository_pipeline to chain both stages in one call. Read-only against the repository; persists the bundle artifact. Returns suspect_files, suspect_symbols, evidence_items, and token reduction stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signalsYesEvidence seeds: issue_text, diagnostics, failing_tests, changed_files, workspace_context.
snapshot_idYesSnapshot id from create_repository_snapshot.
token_budgetNoTotal evidence token budget, 256-32000; defaults to 6000.
repository_idYesSaved repository connector id from list_connectors.
max_snippet_linesNoPer-snippet line cap, 5-200; defaults to 40.
max_evidence_itemsNoEvidence item cap, 1-64; defaults to 16.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.3
    • addedInput schema / properties / max_evidence_items / description
      Added value: +"Evidence item cap, 1-64; defaults to 16."
    • addedInput schema / properties / max_snippet_lines / description
      Added value: +"Per-snippet line cap, 5-200; defaults to 40."
    • addedInput schema / properties / repository_id / description
      Added value: +"Saved repository connector id from list_connectors."
    • addedInput schema / properties / signals / description
      Added value: +"Evidence seeds: issue_text, diagnostics, failing_tests, changed_files, workspace_context."
    • addedInput schema / properties / snapshot_id / description
      Added value: +"Snapshot id from create_repository_snapshot."
    • addedInput schema / properties / token_budget / description
      Added value: +"Total evidence token budget, 256-32000; defaults to 6000."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations provide no safety signals (readOnlyHint, idempotentHint, destructiveHint all false), so the description carries the burden. It discloses the side effect ('persists the bundle artifact') while clarifying it is 'read-only against the repository', plus describes costing and return behavior. This does not contradict the annotations.

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?

Five concise sentences, with the core purpose front-loaded. Every sentence contributes: purpose, signal inputs, downstream pipeline relationship, side effect, and return fields. No filler or 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?

Given there is no output schema, the explicit return-field list (suspect_files, suspect_symbols, evidence_items, token reduction stats) is valuable. The side effect and pipeline role are also covered. Minor gaps like failure modes or artifact overwrite behavior prevent a perfect score.

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 description coverage is 100%, so the baseline is 3. The description adds useful meaning for signals by listing issue_text, diagnostics, failing_tests, changed_files, and workspace_context, but most parameter ranges, defaults, and provenance are already documented in the schema.

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?

The description uses a specific verb ('Condense') and resource ('one repository snapshot into a bounded workspace evidence bundle'), and clearly states it produces ranked, scored, budget-capped evidence for the planner. It also distinguishes itself from the downstream create_repository_decision_plan and the chaining run_repository_pipeline.

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?

The description explicitly says the returned bundle is the required input to create_repository_decision_plan and that run_repository_pipeline chains both stages in one call, giving an agent clear routing context. It does not provide explicit when-not-to-use exclusions, but the pipeline context is strong.

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