Skip to main content
Glama

AICraft Injection Process

optimize

Adjust the current process for one defect. Costs 1 call. Required: defect_info with desc set to an engine code, and current_params.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "optimize"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavioral trait: the operation costs 1 call. It does not state whether the adjustment is reversible, what permissions are required, or what happens to the previous process state when it is overwritten.

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?

Three short sentences, front-loaded with the action and followed by cost and requirements. No filler or hedging; the only cost is that the brevity leaves terms like 'process' undefined.

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?

This is a mutation tool with no annotations, no output schema, and an essentially undocumented input schema. The description names required inputs but omits side effects, the response shape, and any failure conditions, so an agent cannot predict the result of calling it.

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?

The schema is an empty object with additionalProperties=true, so it documents nothing; the description compensates by naming the required inputs and pinning defect_info.desc to an engine code, which is real added meaning. It still leaves current_params and the rest of defect_info's structure unexplained, so the compensation is partial.

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 verb 'adjust' and the object 'the current process' are stated, along with a scope limitation ('for one defect'). However, 'process' is never defined and 'adjust' could mean many things, so an agent cannot tell precisely what the tool changes or how it differs from siblings like first_shot or schema.

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?

'for one defect' implies a single-defect granularity, which is a weak usage hint. There is no explicit when-to-use, when-not-to-use, or alternative named among the siblings, so the agent must infer the choice entirely.

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.