feat: surface MCP asset descriptions and metadata in readable output @W-23572634 - #464
Merged
setu4993 merged 3 commits intoJul 28, 2026
Conversation
Christian-Vallejos
force-pushed
the
t/api-catalog/mcp-asset-descriptions
branch
from
July 24, 2026 17:08
54203ce to
1ef5f77
Compare
@W-23572634@ The Connect API already returns descriptions, labels, auth type and (on fetch) a per-tool security warning, but the human-readable tables dropped them. This brings `sf agent mcp` output to parity with the API so a user can review a tool before approving it, without needing --json. - fetch / asset list / asset replace / create: add Label + Description columns (create now prints the discovered-asset table instead of just a count). - fetch: add a Security Warning column (only /fetch populates it). - list / get: add Auth Type + Description. --json output is unchanged (it always carried the full object). Requires @salesforce/agents with the securityWarning field (forcedotcom/agents#322); schemas regenerated for fetch + create. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Christian-Vallejos
force-pushed
the
t/api-catalog/mcp-asset-descriptions
branch
from
July 25, 2026 18:49
1ef5f77 to
a20e285
Compare
Picks up the published securityWarning field on McpFetchedAsset (forcedotcom/agents#322), which the create/fetch asset tables in this PR already surface. Unblocks the type reference now that agents 1.11.0 is out. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Christian-Vallejos
marked this pull request as ready for review
July 28, 2026 13:57
nschejtman
approved these changes
Jul 28, 2026
setu4993
approved these changes
Jul 28, 2026
Christian-Vallejos
changed the title
Setu needs another fix that landed in the agents lib 1.11.1. Co-Authored-By: Claude Opus 4.8 (1M context) <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
3 participants
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.
What
The
sf agent mcpcommands drop several fields that the Connect API already returns, so a user only sees them via--json. This brings the human-readable output to parity with the API — most importantly the per-tool description and security warning, so a tool can be reviewed before it is approved.fetchLabel,Description,Security Warning(only/fetchpopulates it)asset listLabel,Descriptionasset replaceLabel,Description,Agent ActioncreateDiscovered N asset(s)listAuth Type,DescriptiongetAuth Type,Description--jsonoutput is unchanged (it always carried the full object).Why
Before approving an MCP tool as an agent action, a user needs to read its description and any security warning. Today that information is returned by the API but hidden from the default CLI output.
Dependency
securityWarning?: stringonMcpFetchedAssetcomes from feat: add securityWarning to McpFetchedAsset forcedotcom/agents#322, now merged and published in@salesforce/agents@1.11.0.@salesforce/agents^1.10.3 → ^1.11.0(package.json+yarn.lock) to pick up that field — so the create/fetch tables compile and render against the real published type.agent mcp fetch/agent mcp createwere regenerated to include the new field.Test plan
tsc+eslintcleanmocha test/commands/agent/mcp/mcp.test.ts— asset-command tests passing, including added coverage asserting theDescriptionandSecurity Warningcolumns render increateandfetchyarn test:only— 447 passingsnapshot:compare+schema:compare— no changes detectedbuild+testgate green@W-23572634@