Skip to main content
Glama

Parse a URL

parse_url
Read-onlyIdempotent

Split a URL into scheme, host, port, path, decoded query parameters and fragment.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to parse.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds one genuine behavioral fact beyond the annotations: query parameters are returned in decoded form, which affects how an agent consumes the result. It says nothing, however, about what happens with malformed or relative URLs.

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?

A single sentence with no filler that front-loads the action and then lists the output components. Every clause carries information an agent can use.

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?

This is a simple, one-parameter, read-only tool, and the description compensates for the absent output schema by naming the returned fields, including the decoded query string. The only real gap is edge-case behavior for invalid input, which is minor at this complexity level.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents it completely ("The URL to parse."). The description adds no format constraints, acceptable schemes, or handling notes for the input beyond the schema, so the baseline of 3 applies.

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 uses a specific verb ("Split") on a specific resource (a URL) and enumerates exactly which components are produced (scheme, host, port, path, query parameters, fragment). That is far more precise than the title alone. It does not differentiate against siblings, but none of the listed siblings parse URLs, so the omission costs little.

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?

Usage is only implied: an agent can infer it should call this when it needs URL components, but there is no explicit when-to-use or when-not-to-use statement and no pointer to an alternative (e.g., for building or validating URLs). For a single-purpose utility with no real competitors in the catalog, implied usage is adequate.

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.