Skip to main content
Glama
MCP Toolkit

MCP Toolkit

url_inspect

Parse an HTTP(S) URL without fetching it to inspect its components, query parameters, and structure for validation or transformation.

Instructions

Parse an HTTP(S) URL without fetching it.

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_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations at all, the description carries the full behavioral burden, and it discloses only one trait: no network request is made. It says nothing about what parse result is produced (which components are returned, how malformed URLs are treated, whether it throws or returns an error field), which is the information an agent most needs before calling it.

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?

One short sentence, front-loaded with the verb and resource, with the scope-limiting clause placed where it does the most work. Nothing is padded or redundant.

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?

For a simple one-parameter utility with no output schema, the definition is minimally sufficient but leaves a real gap: since no output schema exists, the description should describe the shape of the parsed result. As written, the agent knows what goes in but not what comes out.

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 coverage is 0% — the single 'url' property is typed only as a string with no description. The definition compensates partially by specifying the accepted scheme ('HTTP(S)'), implying that non-HTTP URLs or relative paths are out of scope, but gives no format examples or edge-case guidance.

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 pairs a specific verb ('parse') with a specific resource ('an HTTP(S) URL'), so an agent immediately knows this is a decomposition/analysis operation on a URL string. The 'without fetching it' clause narrows scope versus a network-fetching tool, though it does not name or contrast with any sibling such as url_encode.

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: 'without fetching it' signals this is a local, non-network inspection step rather than retrieval. There is no explicit statement of when to pick this over url_encode or text_analyze, and no mention of prerequisites or the fact that the input must be absolute with an http/https scheme.

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