Skip to main content
Glama
Sign In

OrgGen AI

by ai.orggen
OverviewDiscussionsAdmin

update_data_source

Destructive

Updates the metadata of an existing source (cadence, connectionInfo, extractionLogic). The connectionInfo provided is MERGED key by key into the existing one by default (keys not sent back are kept); connectionInfoMode: 'replace' gives an explicit full replacement. If connectionInfo contains a key that looks like a credential (password/token/secret/api_key/…), even nested at any depth, the WHOLE call is refused with an explicit error naming the offending key — no silent filtering, nothing is written.

Input Schema

NameRequiredDescriptionDefault
idYes
descNo
nameNo
colorKeyNo
sourceTypeNo
connectionInfoNoMERGED into the existing connectionInfo, key by key (update_cell pattern): only the keys provided are written, the others stay. `connectionInfoMode: 'replace'` REPLACES the old one ENTIRELY (keys not sent back are lost).
refreshCadenceNo
extractionLogicNo
expectedProjectIdNoUUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted.
connectionInfoModeNo'merge' (DEFAULT): the `connectionInfo` provided is merged key by key into the existing one, keys not mentioned are kept. 'replace': the `connectionInfo` provided REPLACES the old one ENTIRELY (any key not sent back is lost) — requires `connectionInfo` (an empty `{}` clears everything).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / connectionInfo / description
      Previous value: -"FUSIONNÉ dans le connectionInfo existant, clé par clé (patron update_cell) : seules les clés fournies sont écrites, les autres restent. `connectionInfoMode: 'replace'` REMPLACE l'ancien EN ENTIER (les clés non renvoyées sont perdues)."New value: +"MERGED into the existing connectionInfo, key by key (update_cell pattern): only the keys provided are written, the others stay. `connectionInfoMode: 'replace'` REPLACES the old one ENTIRELY (keys not sent back are lost)."
    • changedInput schema / properties / connectionInfoMode / description
      Previous value: -"'merge' (DÉFAUT) : `connectionInfo` fourni est fusionné clé par clé dans l'existant, les clés non mentionnées sont conservées. 'replace' : `connectionInfo` fourni REMPLACE l'ancien EN ENTIER (toute clé non renvoyée est perdue) — nécessite `connectionInfo` (`{}` vide tout)."New value: +"'merge' (DEFAULT): the `connectionInfo` provided is merged key by key into the existing one, keys not mentioned are kept. 'replace': the `connectionInfo` provided REPLACES the old one ENTIRELY (any key not sent back is lost) — requires `connectionInfo` (an empty `{}` clears everything)."
    • changedInput schema / properties / expectedProjectId / description
      Previous value: -"UUID du projet visé par CET appel. Cible RÉELLEMENT ce projet au lieu du projet de session. Refusé sans rien modifier si l'accès n'est pas accordé."New value: +"UUID of the project targeted by THIS call. ACTUALLY targets this project instead of the session project. Refused without changing anything if access is not granted."
  2. Changed2 schema fields changed
    • changedInput schema / properties / connectionInfo / description
      Previous value: -"FUSIONNÉ dans le connectionInfo existant, clé par clé (patron update_cell) : seules les clés que tu fournis sont écrites, les autres restent. Pour REMPLACER l'ancien EN ENTIER (perdre les clés non renvoyées), passe `connectionInfoMode: 'replace'`."New value: +"FUSIONNÉ dans le connectionInfo existant, clé par clé (patron update_cell) : seules les clés fournies sont écrites, les autres restent. `connectionInfoMode: 'replace'` REMPLACE l'ancien EN ENTIER (les clés non renvoyées sont perdues)."
    • changedInput schema / properties / connectionInfoMode / description
      Previous value: -"'merge' (DÉFAUT) : `connectionInfo` fourni est fusionné clé par clé dans l'existant, les clés non mentionnées sont conservées. 'replace' : `connectionInfo` fourni REMPLACE l'ancien EN ENTIER (toute clé non renvoyée est perdue) — nécessite `connectionInfo` (passe `{}` pour tout vider)."New value: +"'merge' (DÉFAUT) : `connectionInfo` fourni est fusionné clé par clé dans l'existant, les clés non mentionnées sont conservées. 'replace' : `connectionInfo` fourni REMPLACE l'ancien EN ENTIER (toute clé non renvoyée est perdue) — nécessite `connectionInfo` (`{}` vide tout)."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the destructiveHint annotation by spelling out the merge-by-default semantics, that replace loses unlisted keys, and that credential-like keys at any depth cause the whole call to be refused with nothing written. The main omission is whether partial updates to name/desc/sourceType behave like a patch (they must, since only id is required).

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 purpose is front-loaded in the first clause, then the two risky behaviors follow in priority order. The second sentence is long but every clause (any depth, whole call refused, no silent filtering) carries operational weight.

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?

For a destructive 10-parameter mutation with a nested object and no output schema, it covers the highest-risk dimensions: merge default, destructive replace, and credential refusal. It does not describe the success response or whether non-connectionInfo fields are individually optional, but those gaps are modest against the schema.

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 coverage is low (30%) but the description compensates precisely where the risk lies: connectionInfo merge vs. replace semantics and the credential-key refusal rule, plus naming cadence/connectionInfo/extractionLogic. The remaining parameters (desc, name, colorKey, sourceType, refreshCadence) are left to the schema/enums, so it is helpful but not fully compensating.

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?

States a specific verb (updates) plus the exact resource (existing source) and enumerates the mutable fields (cadence, connectionInfo, extractionLogic). It is clearly distinguished from siblings such as add_data_source, delete_data_source, and update_cell.

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?

It explains the choice between merge (default) and replace mode, which is genuine usage guidance for one parameter, but never states when to call this tool versus add_data_source/delete_data_source, nor any prerequisite or when-not condition. Usage is implied by the mutation verb only.

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

All OrgGen AI 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