Skip to main content
Glama

list_analyses

List analyses for the given repository, newest first.

repository_id is the GitHub owner/repo (a repo UUID also works). Mirrors the BranchView's per-branch state. commit_sha is the commit the analysis was refreshed against.

For the common 'fix everything wrong on a branch' workflow, prefer fix_branch — it resolves the latest analysis for you.

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": {
      "repository_id": "<repository_id>"
    },
    "name": "list_analyses"
  }
}

Input Schema

NameRequiredDescriptionDefault
repository_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully states the sort order (newest first) and that results mirror the BranchView's per-branch state, but says nothing about result limits, pagination, authorization needs, or behavior when the repository has no analyses — the sort order alone is thin coverage for an unannotated listing tool.

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 paragraphs, front-loaded with the core action and ordering, then identifier format, then the alternative route. The commit_sha sentence describes a field that the input schema never exposes, which is wasted and mildly confusing text rather than tightening the definition.

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?

An output schema exists, so return-value explanation is rightly omitted, and one parameter is fully explained. What remains missing for a listing tool is volume behavior — result caps, pagination, or how many analyses typically come back — and the stray commit_sha reference slightly muddies what the tool actually accepts.

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 description coverage is 0% for the single required parameter, but the description compensates well, explaining that repository_id is a GitHub 'owner/repo' string while a repo UUID also works. That is meaning an agent could not derive from the schema. It loses a point because it discusses a commit_sha parameter that does not exist in the input schema, leaving ambiguity about what else the call accepts.

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 ('List analyses for the given repository') plus ordering ('newest first') and scoping ('Mirrors the BranchView's per-branch state'), which lets an agent picture exactly what comes back. It also names the workflow sibling it is not for ('prefer fix_branch'), so it is distinguishable without opening schemas.

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 explicit routing guidance for the common case: for the 'fix everything wrong on a branch' workflow, use fix_branch because it resolves the latest analysis itself. That is a real when-to-use-vs-alternative instruction, but there is no general when-not guidance (e.g., when to use this instead of list_repositories to discover a repository_id).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources