Skip to main content
Glama

HTTP 414 uri-too-long

by io.github.sadri-dridi
OverviewDiscussionsAdmin

http-414

Meaning of HTTP 414.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoGit ref name; discarded after the shape check
urlNoHTTPS URL to normalize or cite
cityNoCity name for a public weather hint; discarded after the call
feedNoPublic RSS or Atom URL; titles discarded
hostNoPublic hostname
jsonNoJSON text to validate; discarded after the check
pathNoFile path to check; no disk access
zoneNoIANA timezone name
queryNoSearch text; discarded after the length check
websiteNoPublic https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / website
      Added value: +{
+  "description": "Public https website (homepage domain) to check for agent readiness: robots.txt, llms.txt, sitemap.xml, extractable HTML. Bounded, identified, robots-respecting.",
+  "type": "string"
+}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations present, the description carries the full burden of behavioral disclosure, but it only says 'Meaning of HTTP 414.' It does not explain that parameters are discarded or ignored, that the call is safe and side-effect-free, or what the response format will be. The schema hints at discarding, but the description itself adds little transparency.

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?

The description is only a few words, front-loaded, and contains no filler or redundant phrasing. Its brevity is appropriate for what appears to be a simple informational tool, though it flirts with being too sparse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 unrelated optional parameters, no output schema, no annotations, and a sibling tool with overlapping purpose, a one-line description is not operationally complete. An agent cannot tell whether to call with no arguments, ignore the parameters entirely, or expect a specific textual answer.

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%, so each parameter is at least documented, which establishes a baseline of 3. The tool description adds no parameter-level meaning and, more importantly, never clarifies that the 10 optional parameters are irrelevant to retrieving the HTTP 414 meaning.

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 phrase 'Meaning of HTTP 414' clearly names the resource (HTTP status 414) and the expected kind of result, so an agent can grasp the tool's purpose. It is not as strong as a verb-led description and does not differentiate from the sibling status-catalog, so it misses a 5.

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?

The description gives no guidance about when to choose this tool over status-catalog or any other sibling. It also does not state that the many optional parameters are unnecessary, leaving the intended invocation context to be inferred.

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

All HTTP 414 uri-too-long toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources