ZapifyAPI MCP Server

parse_user_agent

Parse a User-Agent string to extract browser, operating system, and device details.

Instructions

Parse a User-Agent string into browser, OS, device info.

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": {
      "user_agent": "<user_agent>"
    },
    "name": "parse_user_agent"
  }
}

Input Schema

Name	Required	Description	Default
`user_agent`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 3, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the core function. It does not mention return format, error handling on invalid input, or any limitations, making the tool's behavior partially opaque.

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?

The description is a single, well-structured sentence that is appropriately sized and front-loaded. Every word contributes meaning, with no filler or redundancy.

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?

The tool is simple (one parameter, no output schema), so the description provides a basic understanding of purpose and likely output fields. However, it lacks details about return structure, invalid input handling, or any special behaviors, leaving some gaps for a fully complete picture.

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?

The schema has one parameter with no description, and the description adds no additional semantic detail beyond what the parameter name 'user_agent' already implies. There is no example, format specification, or clarification of edge cases.

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?

The description uses a specific verb ('Parse'), a clear resource ('User-Agent string'), and states the resulting outputs (browser, OS, device info). This clearly distinguishes the tool from all siblings, none of which handle user-agent parsing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The intended usage is only implied by the description, not stated directly.

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