Skip to content

feat(resources): add statusOnly parameter to resources_get#1143

Open
Semih702 wants to merge 1 commit into
containers:mainfrom
Semih702:feat/resources-get-status-only
Open

feat(resources): add statusOnly parameter to resources_get#1143
Semih702 wants to merge 1 commit into
containers:mainfrom
Semih702:feat/resources-get-status-only

Conversation

@Semih702

@Semih702 Semih702 commented May 9, 2026

Copy link
Copy Markdown

Add an optional boolean statusOnly parameter to the resources_get tool.
When set to true, only the .status field of the Kubernetes resource is
returned instead of the full object. When the resource has no status field,
an empty object is returned. Default behavior is unchanged.

Changes:

  • pkg/toolsets/core/resources.go: schema definition and handler logic
  • pkg/mcp/resources_test.go: three test scenarios (status returned,
    explicit false, missing status field)

Closes #876

Add an optional boolean parameter to the resources_get tool.
When set to true, only the .status field of the Kubernetes
resource is returned instead of the full object. Resources
without a status field return an empty object.

Closes: containers#876
Signed-off-by: semih702 <semih702do@gmail.com>
@Semih702
Semih702 force-pushed the feat/resources-get-status-only branch from 985a280 to f8bbf53 Compare May 9, 2026 01:01
@Cali0707

Copy link
Copy Markdown
Collaborator

Related to the broader #877 - IMO let's prioritize evaluating the best approach forward there (cc @manusa )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature Request] Add statusOnly parameter to resources_get to reduce context usage

2 participants