Hook Detector

update_agent

Change an agent's name or monthly budget, or pause it. Same as PATCH /v1/agents/{agent_id}.

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": {
      "agent_id": "<agent_id>"
    },
    "name": "update_agent"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`active`	No
`api_key`	No
`agent_id`	Yes
`monthly_budget`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 27, 2026

TDQS

C2.5/5.0

Behavior2/5

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

No annotations are provided. The description correctly implies a mutation operation via the word 'change,' but provides no information on side effects, rate limits, or required permissions, which is especially critical for an API mutation tool.

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, highly concise sentence that front-loads the functional description and uses the common URL structure to ground its purpose efficiently.

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

Completeness1/5

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

Given that there are 5 parameters and 0% schema description coverage, the description is severely lacking. It fails to mention the 'api_key' field at all and provides no behavioral constraints.

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

Parameters1/5

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

Schema coverage is 0%, meaning the description must carry the full burden of meaning. It only lists 3 of the 5 possible update fields (name, budget, active status) and completely fails to explain what the 'api_key' field represents or requires.

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 tool description clearly identifies the core purpose (change agent settings), but it is general and does not differentiate the tool from the numerous 'admin' or 'update' siblings by specific behavior or constraint.

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?

The description lists the specific variables that can be modified (name, monthly budget, and status/pausing) which serves as an implicit usage guide for the parameters. However, it does not offer explicit exclusions or prerequisites.

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

All Hook Detector tools Inspect

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

Need Help?