Skip to main content
Glama
Sign In
Everyday DevTools MCP

Everyday DevTools MCP

by Deependra12349
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

url_decode

Converts percent-encoded URL strings back into readable text. Use it to inspect encoded query parameters, paths, or redirect values without manual unescaping.

Instructions

Decode a percent-encoded URL string.

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": {
      "text": "<text>"
    },
    "name": "url_decode"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full behavioral burden. It confirms the transformation but says nothing about malformed percent sequences, '+' handling, error behavior, or return shape; significant gaps remain for a decoder.

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 front-loaded sentence with no redundant wording. It is appropriately sized for a simple utility.

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 tool the core operation is covered, but without annotations or an output schema the description should do more to explain edge-case behavior and output expectations. It is minimally adequate rather than complete.

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?

The input schema has 0% description coverage for the single required 'text' parameter. The description compensates somewhat by specifying that the input should be a percent-encoded URL string, but it does not name or further constrain the parameter.

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?

States a specific verb ('Decode') and resource ('percent-encoded URL string'), so the operation is unambiguous. It does not explicitly point to url_encode as the inverse sibling, so it falls short of full sibling differentiation.

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?

The description implies use when handling percent-encoded URL strings but gives no explicit when-to-use guidance, prerequisites, or alternatives such as url_encode. For a one-off utility this may be enough, but the guidance is only implied.

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

Deploy Server

Other Tools