Skip to main content
Glama

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

URL parser, parse a URL: split a URL into scheme, host, port, path, query parameters and fragment

url_parse
Read-only

Split a URL into protocol, host, port, path, query parameters (as an object), hash and origin, and report whether the host is an IP address. Use to read query parameters or check a link's host. Example: url=https://example.com:8080/a/b?x=1&y=2#top. 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": {
      "url": "<url>"
    },
    "name": "url_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to parse

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 readOnlyHint=true and destructiveHint=false, so the description's "reads or computes only and changes nothing" is reinforcing rather than new. The genuinely additive content is the billing behavior: $0.01/call, first 25 free, failed calls free, and that repeats are charged — which usefully explains the idempotentHint=false annotation in cost terms. It stops short of describing return shape or error behavior beyond field enumeration.

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?

Front-loaded with the decomposition, then example, then pricing, then safety — a sensible order with no filler. The final clause "each call is charged, so repeats are not free" partially restates the earlier price sentence, a small redundancy in an otherwise tight definition.

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?

With no output schema, the description carries the return-value burden and does so by naming every extracted field including the is-IP flag. For a one-parameter, non-destructive parsing tool, nothing an agent needs before calling 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% for the single required parameter, so the baseline is 3. The worked example (https://example.com:8080/a/b?x=1&y=2#top) adds concrete meaning by showing that port, multi-param query strings and fragments are all valid inputs, which the bare schema line "The URL to parse" does not convey.

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 (split) and resource (a URL) and enumerates exactly what is extracted: protocol, host, port, path, query parameters as an object, hash, origin, plus an is-IP check. That enumeration distinguishes it clearly from decode/encode siblings, which transform rather than decompose a URL.

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?

"Use to read query parameters or check a link's host" gives implied usage contexts, but there is no when-not guidance and no explicit routing to url_decode, url_encode or useragent_parse. The agent can infer the fit from the described outputs but must reason about alternatives itself.

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.