Skip to main content
Glama

neuron

by io.github.conquext

Update Tool

neuron_update_tool
Idempotent

Modify an existing custom API tool's configuration, including its endpoint, authentication, or request template.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUnique identifier (UUID) of the tool to update
nameNoUpdated human-readable name for the tool
typeNoUpdated type of the tool integration
configNoUpdated tool configuration
authTypeNoUpdated authentication type
rateLimitNoUpdated maximum requests per minute
timeoutMsNoUpdated request timeout in milliseconds
descriptionNoUpdated description of the tool's purpose

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / config / properties / asyncConfig
      Added value: +{
+  "additionalProperties": false,
+  "description": "Configuration for async submit-poll-download APIs",
+  "properties": {
+    "completedStatuses": {
+      "description": "Status values indicating completion",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "failedStatuses": {
+      "description": "Status values indicating failure",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "jobIdPath": {
+      "description": "Dot-notation path to extract job ID from initial response",
+      "type": "string"
+    },
+    "maxPollingMs": {
+      "description": "Maximum time to poll before timeout (default: 120000)",
+      "maximum": 300000,
+      "minimum": 5000,
+      "type": "number"
+    },
+    "pollingEndpoint": {
+      "description": "URL template with {{jobId}} placeholder for polling job status",
+      "type": "string"
+    },
+    "pollingIntervalMs": {
+      "description": "Milliseconds between poll requests (default: 2000)",
+      "maximum": 30000,
+      "minimum": 500,
+      "type": "number"
+    },
+    "resultPath": {
+      "description": "Dot-notation path to extract final result from completed response",
+      "type": "string"
+    },
+    "statusPath": {
+      "description": "Dot-notation path to status field in poll response",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed12 schema fields changed
    • changedInput schema / properties / authType / description
      Previous value: -"Updated authentication type (e.g., 'bearer', 'basic', 'apiKey', 'none')"New value: +"Updated authentication type"
    • addedInput schema / properties / authType / enum
      Added value: +[
+  "none",
+  "api_key",
+  "bearer",
+  "basic",
+  "oauth2"
+]
    • changedInput schema / properties / config / description
      Previous value: -"Updated tool configuration for the HTTP endpoint"New value: +"Updated tool configuration"
    • addedInput schema / properties / config / properties / endpoint
      Added value: +{
+  "description": "Updated target HTTP endpoint URL",
+  "type": "string"
+}
    • addedInput schema / properties / config / properties / mcpServerUrl
      Added value: +{
+  "description": "Updated MCP server URL",
+  "type": "string"
+}
    • changedInput schema / properties / config / properties / method / description
      Previous value: -"Updated HTTP method (GET, POST, PUT, DELETE, PATCH)"New value: +"Updated HTTP method"
    • addedInput schema / properties / config / properties / method / enum
      Added value: +[
+  "GET",
+  "POST",
+  "PUT",
+  "PATCH",
+  "DELETE"
+]
    • addedInput schema / properties / config / properties / parametersSchema
      Added value: +{
+  "additionalProperties": {},
+  "description": "Updated JSON Schema for tool parameters",
+  "type": "object"
+}
    • removedInput schema / properties / config / properties / responseMapping
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Updated mapping rules for the API response",
-  "type": "object"
-}
    • removedInput schema / properties / config / properties / url
      Removed value: -{
-  "description": "Updated target HTTP endpoint URL (valid HTTP/HTTPS URL)",
-  "type": "string"
-}
    • addedInput schema / properties / config / properties / webhookUrl
      Added value: +{
+  "description": "Updated webhook URL",
+  "type": "string"
+}
    • addedInput schema / properties / type
      Added value: +{
+  "description": "Updated type of the tool integration",
+  "enum": [
+    "http_api",
+    "webhook",
+    "mcp"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations indicate idempotent and non-destructive, which is consistent. Description doesn't elaborate on side effects, validation, or requirements beyond basic update. No annotation contradiction.

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

Conciseness5/5

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

Single sentence, 16 words, efficient and front-loaded with the action. No filler or redundant information.

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?

Covers the basic update purpose but doesn't mention the full range of configurable fields (rate limit, timeout, description, etc.) or the required id. Could be more comprehensive for a tool with 8 parameters.

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 100%, so schema already describes parameters. Description adds marginal value by naming example parameters (endpoint, auth, request template) but doesn't exceed schema's clarity.

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?

Description uses specific verb 'modify' with resource 'existing custom API tool' and lists aspects like endpoint, authentication, request template. It clearly distinguishes from siblings which update other entities (bots, contacts, etc.) or create tools.

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?

Clearly implies use when updating a custom tool's configuration. Doesn't explicitly state when not to use or mention alternatives like recreating the tool. Could provide more context on prerequisites.

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

All neuron toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation3/5

Most tools are clearly separated by resource type, but there is meaningful overlap in messaging entry points (send_message, send_whatsapp, compose_message, bot_api_send) and contact ingestion/sync tools (import_contacts, populate_contacts, sync_whatsapp_contacts). The descriptions help disambiguate, but with 309 tools an agent will frequently need to read closely to pick the right one.

Naming Consistency4/5

The overwhelming majority of tools follow a consistent verb_noun snake_case pattern: create_*, get_*, list_*, update_*, delete_*. Minor deviations like sales_stats, lead_stats, wallet_balance, and whoami break the pattern slightly, but overall naming is highly predictable.

Tool Count1/5

309 tools is an extreme count for any MCP server, even a broad platform. This creates significant cognitive load and navigation overhead for agents, and far exceeds the well-scoped 3-15 tool range where coherence is strongest.

Completeness4/5

The tool surface is remarkably comprehensive across bots, contacts, campaigns, flows, knowledge bases, personas, marketplace, wallet, and products. Minor gaps exist — lead sources lack update/delete tools, and there is no single get_task or get_webhook alongside their list/update/delete counterparts — but these are workable gaps rather than dead ends.

Resources