AL-Go MCP Server

Search AL-Go Resolved Issues

alg-search-issues

Search the last 100 closed AL-Go issues to find tips and workarounds for Business Central development automation problems.

Instructions

Search the 100 most recently closed AL-Go issues for tips and workarounds

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": {
      "query": "<query>"
    },
    "name": "alg-search-issues"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results to return
`query`	Yes	Search query for issues

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv2.9.0Oct 19, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```
First observedv2.8.0Jul 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose a meaningful limitation — the corpus is capped at the 100 most recently closed issues, so open issues and older resolutions are invisible — but it says nothing about return format, whether issue links/IDs are included, or any rate/permission constraints.

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?

A single front-loaded sentence with no filler; the scope constraint and purpose are both delivered immediately.

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

Completeness3/5

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

For a two-parameter search tool with no annotations and no output schema, the description covers scope but not result shape or search behavior. An agent can invoke it correctly but cannot predict what a result contains or how ranking works.

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% for both parameters, so the baseline is 3. The description adds no query syntax, matching behavior, or relevance-ranking detail beyond the schema, and its mention of '100 issues' is in mild tension with the limit parameter's max of 50.

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 gives a specific verb (Search) and resource (AL-Go issues), plus a scope qualifier (100 most recently closed) and a purpose (tips and workarounds). It implicitly distinguishes itself from sibling search tools (alg-search-docs, alg-search-discussions) by naming the issue corpus, though it never routes explicitly to those alternatives.

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

Usage Guidelines3/5

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

It hints at when to use it (looking for tips and workarounds), which implies troubleshooting intent, but names no alternatives and gives no when-not guidance despite five sibling search tools existing. Usage is inferred rather than stated.

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

Deploy Server