Skip to main content
Glama

Log a delegation

log_delegation

Records a task delegation you just made and returns an ID for logging its outcome later, enabling tracking of provider, model, and task details.

Instructions

Optional. Record a delegate_task you just made; returns a delegationId to pass to log_outcome later. log_outcome also works without it.

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": {
      "taskType": "<taskType>",
      "providerInstanceId": "<providerInstanceId>",
      "model": "<model>"
    },
    "name": "log_delegation"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
optionsNo
summaryNoShort task summary (kept to 200 characters). Avoid secrets.
taskTypeYes
childThreadIdNo
recommendedRankNo1-based rank of the recommend_model candidate you used; null if you chose something else.
providerInstanceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description usefully adds that the call returns a delegationId consumed later and that omitting it is valid, but it does not say what happens on repeat calls despite idempotentHint=false, nor whether records are persisted/retrievable elsewhere.

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?

Two short sentences with no filler, and the critical qualifier "Optional" is front-loaded before the mechanics. Every clause carries information the agent needs.

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?

For a 7-parameter write tool with sparse schema descriptions and no output schema, the description is too thin: it neglects most required inputs and the meaning of options/childThreadId/recommendedRank. Only the optionality and the delegationId return value are adequately covered.

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

Parameters2/5

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

Schema coverage is only 29% across 7 parameters; the required taskType, providerInstanceId, and model have no documented meaning anywhere, and options and childThreadId are likewise unexplained. The description contributes nothing to parameter semantics beyond naming delegationId as an output, leaving the agent to infer required values.

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?

"Record a delegate_task you just made" gives a specific verb and resource, and the description explains the resulting delegationId and its link to log_outcome. It differentiates reasonably from the log_outcome sibling, though it never explains what a delegate_task is or how it relates to recommend_model.

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?

"Optional" plus "log_outcome also works without it" tells the agent it is safe to skip this call, which is real guidance. However, it gives no positive condition for when logging a delegation is worth doing (e.g., to preserve traceability or correlate with log_outcome/get_stats), so the agent must guess at the benefit.

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

Deploy Server

Other Tools