Skip to main content
Glama

HSL tuple shape

by io.github.sadri-dridi
OverviewAdmin

compatibility

Show how this request is classified. No identifiers are retained.

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

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City name for a public weather hint; discarded after the call",
+  "type": "string"
+}
    • addedInput schema / properties / feed
      Added value: +{
+  "description": "Public RSS or Atom URL; titles discarded",
+  "type": "string"
+}
    • addedInput schema / properties / path
      Added value: +{
+  "description": "File path to check; no disk access",
+  "type": "string"
+}
    • addedInput schema / properties / query
      Added value: +{
+  "description": "Search text; discarded after the length check",
+  "type": "string"
+}
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "Git ref name; discarded after the shape check",
+  "type": "string"
+}
  2. First observed

TDQS

C2.2/5.0
Behavior2/5

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

The only behavioral disclosure is 'No identifiers are retained,' which gives some privacy-relevant information. However, with no annotations provided, the description still fails to state whether the operation is read-only, what data is processed, or what side effects might occur.

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 short and direct, with no redundant wording or filler. It opens with the main action and then adds a privacy note, which is an efficient structure.

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?

The description is too minimal for a tool with four optional parameters and no output schema. It does not explain how the parameters are used, what classification result is returned, or what makes an input compatible, leaving critical context missing.

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 already provides 100% parameter coverage with definitions like 'HTTPS URL to normalize or cite' and 'JSON text to validate.' The tool description adds no additional context about how these parameters relate to 'classification' or 'compatibility,' so it does not improve on the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Show how this request is classified' but never defines what 'classified' means, what kind of request is involved, or what output is produced. It does not clearly state the tool's core operation or resource, and the name 'compatibility' is not reflected in the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool instead of a sibling tool. The description does not mention alternatives, prerequisites, or typical scenarios, leaving the agent to guess from the tool name and parameters.

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

All HSL tuple shape toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources