Skip to main content
Glama
Sign In

Outil.io

by io.outil
OverviewDiscussionsAdmin

Update collection

update_collection
Destructive

Remplacer la configuration avec sa version courante, hors collecte queued/running. Les colonnes historiques gardent leur clé et leur type. Les clés API restent dans les connexions de l’agent, jamais dans la 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>",
      "version": "<version>",
      "config": "<config>"
    },
    "name": "update_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
configYes
versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior4/5

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

Beyond the destructiveHint annotation, the description adds real behavioral contract: the operation is blocked while the collection is queued or running, historical columns retain their key and type, and API keys deliberately never live in the configuration. That is meaningful consequence-and-precondition detail an agent could not get from annotations alone.

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?

Three compact sentences, front-loaded with the core action and the main precondition. Dense but every clause carries information; the telegraphic style is the only weakness.

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

Completeness3/5

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

For a destructive, nested-object mutation with no output schema, the description covers preconditions and data retention but omits the one thing that matters most operationally: what happens on a version mismatch and what a conforming config looks like. Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with three required parameters (id, config, version), and the description does not compensate. It hints at 'version courante' but never says whether version is a concurrency guard that fails on mismatch, nor what shape config must take.

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 says it replaces the configuration with its current version, which loosely maps to a mutation on a collection, but it never states what a 'configuration' comprises or how this differs from update_collection_row or set_collection_state. The verb+resource pair is inferable but the object being replaced is opaque.

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 only usage condition given is the exclusion of queued/running collections, which is useful but negative-only. There is no positive statement of when an agent should choose this over claiming, describing, or row-level updating a collection, despite many adjacent siblings.

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

All Outil.io 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