Skip to main content
Glama

update_tool

Update an existing custom HTTP tool. Omitted fields are preserved. Use when changing URL, method, headers, or schemas. Auth values should use "{{SECRET_NAME}}". Registered vendor URLs belong in metaphor.integration, not execute.url.

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": "update_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
nameNo
executeNoHTTP execute config. May include url, method, headers, and auth (bearer/basic/api-key with {{SECRET_NAME}}).
descriptionNo
inputSchemaNo
outputSchemaNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the description's job is to add context — which it does: omit-to-preserve semantics, the {{SECRET_NAME}} templating requirement for auth values, and the rule that vendor URLs go in metaphor.integration rather than execute.url. It does not describe permission requirements or what the response contains, but the mutation behavior is well disclosed.

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?

Four short sentences, each carrying a distinct constraint: what it does, patch semantics, the change-scope trigger, and two guardrails. Nothing repeats the name or the annotations.

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 mutation tool with nested objects, no output schema, and poor schema coverage, the description covers the risky parts (secrets, URL placement, field preservation) but says nothing about idempotency, whether `id` is immutable, or failure modes. Adequate, not complete.

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 only 17% across 6 parameters, so the description must compensate. It clarifies the nested execute fields (url, method, headers, auth templating) and mentions schemas, but leaves the required `id`, `name`, and `description` unexplained, so half the surface is still undocumented.

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

Purpose4/5

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

"Update an existing custom HTTP tool" names a specific verb and resource, and the following sentence adds patch semantics ("Omitted fields are preserved"). It is distinguishable from create_tool/delete_tool by verb alone, though it never explicitly contrasts itself with those siblings.

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

Usage Guidelines4/5

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

"Use when changing URL, method, headers, or schemas" gives an explicit trigger condition, and a negative constraint is added for vendor URLs. It does not state when to prefer create_tool instead, but the usage context is clear without it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources