Repository navigation
knowledge(web-services): describe API objects intended for MCP tools - #233
Draft
Javier Armesto Gonzalez (javiarmesto) wants to merge 2 commits into
Draft
Javier Armesto Gonzalez (javiarmesto) wants to merge 2 commits into
Javier Armesto Gonzalez (javiarmesto) wants to merge 2 commits into
Conversation
…t for MCP tools The Business Central MCP server takes the tool description from AboutText, then EntitySetCaption, then EntityName. API pages without AboutText reach agents as a bare entity name. LLMs treat AboutText as a UI teaching-tip property and omit it on API objects; no analyzer flags it. Observed in 13 of 22 generated solutions of a read-only SalesMargin query API. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
API objects intended for the Business Central MCP server can expose a bare entity caption where an agent needs to understand document filters or computed values. Add web-services knowledge for the documented description precedence:
AboutText,EntitySetCaption, then camel-casedEntityName. The good/bad samples cover both API pages and queries, with descriptions and actual document-type filters kept consistent.The article preserves valid alternatives: missing
AboutTextis not a defect when the fallback is adequate or MCP use is not established, andAboutTitleis not required solely for MCP. Sources include the Learn API page/query documentation and a pinned Microsoft API query withAboutTextand noAboutTitle. Its scope is BC 28+ online environments with the relevant MCP support; it does not claim that extraction first appeared in 28.0 or cover the earlier preview.The contribution is motivated by a 22-run API generation evaluation whose syntax rubric flagged AboutText omissions in 13 runs, including one incomplete solution. These are omission flags, not measured tool-selection failures. The missing metadata is not diagnosed by the tested standard analyzers. The owning domain is web-services because the concern is the API-to-tool metadata contract, distinct from UI teaching tips.
Validation:
The review-skill edit only selects this knowledge; the facts and exceptions remain in the article. No stable protocol changes or customer-specific code are included.