GoClaw MCP Server

goclaw_provider_update

Modify an LLM provider's configuration in GoClaw MCP Server by updating API keys, base URLs, model lists, or enabling/disabling providers.

Instructions

Update an LLM provider's configuration

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description
`id`	Yes	Provider ID
`name`	No	New name
`api_key`	No	New API key
`base_url`	No	New base URL
`models`	No	Updated model list
`enabled`	No	Enable/disable provider

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 15, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Update' implies a mutation operation, it doesn't describe what happens on success/failure, whether changes are reversible, if it requires specific permissions, or any rate limits/constraints. This leaves significant gaps for a tool that modifies provider configurations.

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?

The description is a single, efficient sentence that gets straight to the point without unnecessary words. However, it could be slightly more specific (e.g., 'Update configuration fields for an existing LLM provider') to better distinguish from create operations.

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

Completeness2/5

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

For a mutation tool with 6 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what 'configuration' entails, what happens when fields are omitted, or what the tool returns. Given the complexity and lack of structured metadata, more context is needed.

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 the schema already documents all 6 parameters thoroughly. The description adds no additional parameter semantics beyond implying these are configuration fields that can be updated. This meets the baseline expectation when schema coverage is high.

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

Purpose3/5

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

The description 'Update an LLM provider's configuration' clearly states the action (update) and target (LLM provider configuration), which is better than a tautology. However, it doesn't specify what aspects of configuration can be updated or differentiate this from sibling tools like goclaw_provider_create or goclaw_provider_delete beyond the basic verb.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing provider ID), when to choose update over create/delete, or any constraints like which fields are optional vs. required beyond the schema's 'id' requirement.

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

Deploy Server