Skip to main content
Glama

Parse URL

bursia_url_parse
Read-onlyIdempotent

Split a URL into protocol, host, port, path, query parameters and fragment. Returns each part as a field. Pure computation, 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": "bursia_url_parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesA full URL, e.g. https://example.com/a?b=1#c.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / url / description
      Added value: +"A full URL, e.g. https://example.com/a?b=1#c."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description still adds useful context the annotations do not: 'pure computation, free' tells the agent there is no network call and no credit cost, and 'returns each part as a field' discloses the response shape. It stops short of saying what happens with a malformed or relative URL.

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?

Three short sentences, zero filler, with the operation and its outputs front-loaded before the cost/caveat note. Every sentence carries distinct information.

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?

There is no output schema, but the description compensates by listing the returned fields, which is the key information an agent needs. Minor gap: it does not say how absent components (no port, no fragment) are represented, or what a malformed URL produces.

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% and the single parameter already carries an example ('https://example.com/a?b=1#c'), so the schema does the heavy lifting. The description adds nothing about the parameter beyond what the schema states, which is the expected baseline-3 case for one fully documented parameter.

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 (URL) and enumerates exactly the parts produced: protocol, host, port, path, query parameters, fragment. That level of precision makes it trivially distinguishable from the nearest sibling, bursia_url_encode, which does the inverse operation.

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 statement of when to use this versus alternatives, no note about when parsing is unnecessary (e.g. if the agent only needs encoding, it should call bursia_url_encode). Usage is only implied by the tool name and the word 'URL'.

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.

Resources