Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

User agent parser: browser, OS, device and bots

useragent_parse
Read-only

Parse a User-Agent string into browser and version, operating system and version, device type (desktop, mobile, tablet or bot) and, for crawlers, which bot it is: Googlebot, Bingbot, GPTBot, ClaudeBot, PerplexityBot, social previewers, SEO crawlers and HTTP libraries such as curl or python-requests. Local rules, no outside service. Use to read access logs, segment traffic or spot AI crawlers. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "ua": "<ua>"
    },
    "name": "useragent_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
uaYesThe User-Agent string

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?

Annotations already declare readOnly=true, destructive=false, openWorld=false, so the safety profile is covered; the description adds genuine context beyond that by announcing local rule-based processing with no outside service and a per-call price model with a free tier and free failures, and it explains why repeats are not free (consistent with idempotentHint=false). It does not say what happens when a UA is unrecognized or malformed, which is the main remaining behavioral gap for a parser.

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?

Front-loaded with the core action and outputs, then usage, then pricing and safety. The bot enumeration is long but earns its place by defining the classification scope; the pricing and read-only notes are compressed into tight clauses with no filler.

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

Completeness4/5

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

With one required parameter, no output schema, and annotations covering safety, the description carries the right load: it enumerates returned fields, states processing locality, and discloses cost. Only the edge-case behavior on unparseable input is left unspecified.

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 100% and the single 'ua' parameter is documented in the schema, so the baseline is 3. The description's bot list lightly signals what kinds of strings are recognized but adds no syntax, length, or format guidance beyond the schema.

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?

Specific verb plus resource ('Parse a User-Agent string') followed by an explicit enumeration of the outputs: browser and version, OS and version, device type, and named bot detection. An agent can distinguish this from a sibling like url_parse because the description names exactly what input it consumes and what classification it produces.

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 concrete usage contexts ('read access logs, segment traffic or spot AI crawlers'), which tells an agent when this is the right tool. It stops short of naming an alternative or an explicit when-not condition, so it sits below the top band.

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.