What your coding agent can read
- Sessions and interactions, including cost, tokens, turns, duration, latency, and input previews.
- Issues and remediation, including rules, severity, affected files, code snippets, evidence, and remediation guidance.
- Inventory, including agents, models, tools, and MCP servers, along with related issues and code locations.
- Guardrails, including policies and counts of traffic by guardrail outcome, such as blocked or redacted.
- Evaluations, including definitions, evaluation health, score trends, and results from individual runs.
- Optimizations, including the confidence level for each and, for most, the estimated savings.
Workspace
Sessions and interactions
Costs are estimates, based on each model’s published price or the rate your organization has set for it. A model with no price shows a cost of $0.
Session and interaction data includes prompts, responses, and input previews, which can contain secrets or customer data. Don’t copy them into pull requests or tickets.
Guardrails
The guardrail count, outcome, and category tools can scope their results to one agent with an agent ID.
Evaluations
Issues and remediation
If
find_issues_for_file returns complete: false, it stopped before checking every issue. Treat the result as unknown rather than clean. It checks up to 50 issues by default, and up to 500 if you ask for more.
Inventory
Cost optimization
These tools read the optimizations from Switch ROI, the Switch Trust capability that shows what each agent costs and recommends how to make it cheaper. That’s where theroi in their names comes from.
Not available through the MCP server
The Switch Trust API also provides cost data that the MCP server doesn’t expose, including cost summaries, spend caps, burn rate, and model pricing. Read that information in Switch Trust or call the API directly.Next steps
Optimize agents
Put these tools to work on an expensive agent, end to end
Connect your coding agent
Set up the server in Claude Code, Cursor, or VS Code

