Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Set agent model

set_agent_model

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "set_agent_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNosonnet is the default; opus is more capable and uses more credits; gpt-sol uses them at the sonnet rate.
on_behalf_ofNoA teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.
use_own_anthropic_keyNoFalse pauses the user's connected Anthropic key, so Claude models run on Sliq credits at the full rate; True resumes it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."New value: +"A teammate's email, or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two behaviors an agent could not infer: the update is partial ('only what you pass changes') and takes effect from the next message or run on. It also supplies a returns block even though no output schema exists, though it says nothing about permissions or credit impact beyond what the schema hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded summary with the mutation and effective timing in the first two sentences, then a short returns block. No filler, though the XML-ish wrapper tags add slight overhead relative to the short prose.

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

Completeness4/5

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

All three optional parameters are fully documented at the schema level, no output schema exists and the description compensates with a returns block, and the temporal scope of the change is stated. Missing only guidance on side effects such as credit or permission implications when switching models.

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%, so parameter meaning is already carried by the schema (including credit-cost notes for opus and the pause semantics for use_own_anthropic_key). The description adds only the general partial-update rule, not param-level detail, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a precise verb and resource pair — change the model chats/agents run on, or pause/resume the user's own Anthropic API key — which distinguishes it from settings-adjacent siblings such as set_activity_hours or get_settings.

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?

Usage context is implied rather than stated: it is a settings mutation, and the schema notes that omitting on_behalf_of acts on your own account. There is no explicit 'when to use this vs update_agent/create_agent' routing or suggestion to read current state first.

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

All Sliq toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources