Skip to main content
Glama

neuron

by io.github.conquext

Create Tool

neuron_create_tool

Create a custom API tool that the bot can invoke during conversations to fetch external data or trigger actions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable name for the tool
typeYesType of the tool integration
botIdYesUnique identifier (UUID) of the bot to create the tool for
configYesTool configuration specifying the endpoint and request details
authTypeNoAuthentication type for the endpoint
rateLimitNoMaximum number of requests per minute allowed for this tool
timeoutMsNoRequest timeout in milliseconds (default: 30000)
descriptionYesDescription of what the tool does and when the bot should use it

Schema Changelog

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

  1. Changed3 schema fields changed
    • addedInput schema / properties / config / properties / asyncConfig
      Added value: +{
+  "additionalProperties": false,
+  "description": "Configuration for async submit-poll-download APIs like fal.ai and Replicate",
+  "properties": {
+    "completedStatuses": {
+      "description": "Status values indicating completion (e.g. ['COMPLETED', 'succeeded'])",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "failedStatuses": {
+      "description": "Status values indicating failure (e.g. ['FAILED', 'failed', 'canceled'])",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "jobIdPath": {
+      "description": "Dot-notation path to extract job ID from initial response (e.g. 'id', 'request_id')",
+      "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 (e.g. 'output')",
+      "type": "string"
+    },
+    "statusPath": {
+      "description": "Dot-notation path to status field in poll response (e.g. 'status')",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
    • addedInput schema / properties / description / maxLength
      Added value: +1000
    • addedInput schema / properties / description / minLength
      Added value: +1
  2. Changed15 schema fields changed
    • changedInput schema / properties / authType / description
      Previous value: -"Authentication type for the endpoint (e.g., 'bearer', 'basic', 'apiKey', 'none')"New value: +"Authentication type for the endpoint"
    • addedInput schema / properties / authType / enum
      Added value: +[
+  "none",
+  "api_key",
+  "bearer",
+  "basic",
+  "oauth2"
+]
    • changedInput schema / properties / config / description
      Previous value: -"Tool configuration specifying the HTTP endpoint and request details"New value: +"Tool configuration specifying the endpoint and request details"
    • addedInput schema / properties / config / properties / endpoint
      Added value: +{
+  "description": "Target HTTP endpoint URL for http_api tools",
+  "type": "string"
+}
    • addedInput schema / properties / config / properties / mcpServerUrl
      Added value: +{
+  "description": "MCP server URL for mcp-type tools",
+  "type": "string"
+}
    • changedInput schema / properties / config / properties / method / description
      Previous value: -"HTTP method to use (GET, POST, PUT, DELETE, PATCH)"New value: +"HTTP method to use"
    • addedInput schema / properties / config / properties / method / enum
      Added value: +[
+  "GET",
+  "POST",
+  "PUT",
+  "PATCH",
+  "DELETE"
+]
    • addedInput schema / properties / config / properties / parametersSchema
      Added value: +{
+  "additionalProperties": {},
+  "description": "JSON Schema describing the parameters the tool accepts",
+  "type": "object"
+}
    • removedInput schema / properties / config / properties / responseMapping
      Removed value: -{
-  "additionalProperties": {},
-  "description": "Mapping rules for extracting and formatting the API response",
-  "type": "object"
-}
    • removedInput schema / properties / config / properties / url
      Removed value: -{
-  "description": "Target HTTP endpoint URL (valid HTTP/HTTPS URL)",
-  "type": "string"
-}
    • addedInput schema / properties / config / properties / webhookUrl
      Added value: +{
+  "description": "Webhook URL for webhook-type tools",
+  "type": "string"
+}
    • removedInput schema / properties / config / required
      Removed value: -[
-  "url",
-  "method"
-]
    • changedInput schema / properties / type / description
      Previous value: -"Type of the tool integration (e.g., 'http', 'webhook')"New value: +"Type of the tool integration"
    • addedInput schema / properties / type / enum
      Added value: +[
+  "http_api",
+  "webhook",
+  "mcp"
+]
    • changedInput schema / required
      Previous value: -[
-  "botId",
-  "name",
-  "type",
-  "config"
-]New value: +[
+  "botId",
+  "name",
+  "description",
+  "type",
+  "config"
+]
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true. The description adds that it creates a tool for bot use, but does not disclose any side effects, limits, or lifecycle implications beyond what annotations already suggest.

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?

The description is a single sentence that clearly conveys the core purpose. It is front-loaded with the action and resource, making it efficient and easy to parse.

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?

The tool has complex nested config and 8 parameters, yet the description provides no information about lifecycle, testing, or how the created tool integrates with the bot. It is insufficient for an agent to fully understand the tool's role in the workflow.

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?

With 100% schema coverage, all parameters are described in the schema. The description adds no additional meaning or context about parameters, so baseline score of 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 description clearly states it creates a custom API tool for a bot to fetch external data or trigger actions. It uses a specific verb and resource, and distinguishes from other 'create' tools by specifying 'tool' as the resource.

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?

No explicit guidance on when to use this tool versus alternatives like update_tool or test_tool. It does not mention when not to use it or provide context for selecting this tool over built-in tools.

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