get_user_agent
Read-onlyIdempotent
The caller's User-Agent string.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
IP Address API
by app.ip
TDQS
B3.4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint. Description adds the output format (User-Agent string), which is useful. No extra behavioral details beyond what annotations provide.
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?
Single sentence, no fluff. Slightly under-specified (could include a verb), but efficient for the simplicity of the tool.
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?
For a zero-parameter tool with clear annotations, the description adequately specifies the return value. Lacks only a verb to be fully contextual.
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?
No parameters exist, and schema coverage is 100%. The description correctly adds nothing about parameters, as none are required.
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?
Description clearly identifies the resource (User-Agent string) but lacks an explicit verb. The tool name 'get_user_agent' supplies the action, making the purpose understandable.
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?
No guidance on when to use this tool vs alternatives like 'get_headers', which may also contain the User-Agent. The description does not provide context for tool selection.
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.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool targets a unique aspect of the caller's request or IP information (ASN, headers, IP, location, security, timezone, user agent, coordinates) with no overlap.
Naming Consistency5/5
All tools follow a consistent 'get_' prefix followed by a clear noun (e.g., get_asn, get_headers), making naming predictable and uniform.
Tool Count5/5
With 8 tools, the server provides a focused set of self-service IP and request data operations without being sparse or bloated.
Completeness5/5
The tool set covers all typical aspects of a caller's IP/request information (IP, location, timezone, security, headers, user agent, ASN, coordinates) with no obvious gaps.