Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Parse User-Agent and Client Hints

web-technology_user-agent-parse
Read-onlyIdempotent

Parse a User-Agent with uap-core patterns into browser, OS and device, optionally overriding with Client Hints. Price $0.02 USDC. POST /api/v1/web-technology/user-agent-parse. An unpaid call returns the x402 payment terms and does not run.

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": {
      "userAgent": "<userAgent>"
    },
    "name": "web-technology_user-agent-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
userAgentYesuserAgent, string, length 1 to 2000. Required.
clientHintsNoclientHints, object. Optional.

Output Schema

NameRequiredDescriptionDefault
osNoos. Object.
deviceNodevice. Object.
browserNobrowser. Object.
sourcesNosources. Array.
reducedUaNoreducedUa. Boolean.
limitationsNolimitations. Array.
clientHintsAppliedNoclientHintsApplied. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses two things the annotations cannot: that the call costs $0.02 USDC and that an unpaid call returns x402 payment terms without executing. It also implies deterministic pattern matching via uap-core, which tells the agent results are rule-based rather than heuristic.

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?

Four short sentences, front-loaded with what the tool does, then cost, endpoint, and payment failure mode. No filler. The HTTP path is arguably redundant for an MCP caller but costs little and aids traceability.

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

Completeness5/5

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

Output schema exists, annotations cover the safety profile, and both parameters are schema-documented, so the description only needed to cover purpose, cost, and override semantics, all of which it does. Nothing required to call the tool correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, and the description adds real value by explaining the relationship between the two parameters: Client Hints optionally override the UA-derived values. That precedence rule is not stated anywhere in the schema, which only labels clientHints as an optional object. It still does not say which hint keys are recognized.

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

Purpose5/5

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

States a specific verb (Parse), a specific input (User-Agent), the engine (uap-core patterns), and the exact output fields produced (browser, OS, device), plus the Client Hints override. That detail makes it clearly distinguishable from siblings like crawler-identify or technology-detect without opening the schema.

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?

Usage is implied: send a UA string, optionally with Client Hints to refine the result. There is no explicit when-to-use versus when-not guidance and no named alternative for related tasks such as crawler identification, so the agent must infer the boundary from the purpose sentence alone.

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