Skip to main content
Glama

get_actual_user_agent

Retrieve the actual User-Agent from an existing task by task_id, or select a provider-documented DataDome User-Agent by platform, browser, and major version.

Instructions

Read solution.userAgent from an existing task of any type when task_id is supplied.

A ready result without a User-Agent returns null. Without task_id, select a provider-documented DataDome User-Agent by platform, browser and major.

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

Input Schema

NameRequiredDescriptionDefault
majorNo
browserNochrome
task_idNo
platformNowindows

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the burden and does disclose the important non-obvious trait that a ready result lacking a User-Agent yields null, plus that the fallback list is provider-documented rather than arbitrary. It omits what happens if task_id refers to an unfinished or invalid task, and whether any auth is needed.

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?

Two short sentences, mode logic front-loaded, no filler. The line wrapping splits the second sentence awkwardly but no content is wasted.

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?

An output schema exists so return shape need not be described, and the description correctly focuses on mode semantics and the null case. For a 4-parameter tool with zero schema documentation, however, the unstated valid values for platform/browser and the behavior on non-ready tasks leave real gaps.

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 coverage is 0%, so the description must compensate. It does explain the role split — task_id switches modes, while platform, browser and major drive the fallback selection — but it gives no indication of valid platform/browser values or the meaning of major beyond 'major version', leaving the enum-less defaults unexplained.

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?

States a specific resource and path (solution.userAgent on an existing task) plus a second mode (pick a provider-documented DataDome User-Agent). The dual behavior is spelled out rather than left to the name. It stops short of naming a sibling tool, so it is clear but not sibling-differentiated.

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?

Gives explicit mode-selection guidance: supply task_id to read from a task, omit it to select from the provider-documented list keyed by platform/browser/major. There are no explicit exclusions or named alternatives, but the when-to-use condition for each branch is unambiguous.

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