Skip to main content
Glama
Sign In

APIVerve

by com.apiverve
OverviewDiscussionsAdmin

User Agent Generator

UserAgentGenerator
Read-only

User Agent Generator: User Agent Generator creates realistic user agent strings for desktop, mobile, and tablet devices. Each request outputs the complete string with parsed browser and operating system names and versions, while paid plans add engine and CPU details. (Cost: 1 credit)

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

Input Schema

NameRequiredDescriptionDefault
osNoOnly user agents of this operating system. iPads send the macOS desktop user agent
deviceNoThe device type: desktop, mobile (phones) or tabletdesktop
browserNoOnly user agents of this browser

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoError message, null on success
statusNo"ok" on success

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the read-only/open-world annotations, the description discloses what each result contains (full UA string with parsed browser and OS name/version), that engine and CPU details are plan-gated, and that each call costs 1 credit. It does not state whether results are randomized per request or whether repeated identical inputs return the same string, which is the main behavioral question for a generator.

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 sentences, front-loaded with the core action, and the credit cost is appended as a parenthetical rather than buried. The only waste is the redundant echo of the tool name at the start ('User Agent Generator: User Agent Generator creates...').

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 all three parameters optional and fully documented in the schema, plus an output schema present, the description only needs to frame purpose and cost — both of which it covers. The remaining gap is determinism/randomness behavior, which matters for a generator but is not addressed.

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 description coverage is 100%, including the non-obvious iPad/macOS note, so the baseline is 3. The description adds nothing about how os, device, and browser interact or what happens when they conflict, leaving the schema to carry all parameter meaning.

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?

The description gives a specific verb and resource ('creates realistic user agent strings') plus the supported device classes (desktop, mobile, tablet), which is clear enough to distinguish it from most siblings. It does not name the obvious counterpart, UserAgentParser, so an agent must infer that this tool produces strings rather than decoding them.

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?

The use case (obtaining UA strings for a given device) is implied by the description and schema parameters, but there is no explicit when-to-use statement and no mention of the alternative UserAgentParser. There are also no prerequisites or exclusions noted.

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

All APIVerve toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources