Skip to main content
Glama

Volt-amperes to watts, number discarded

by io.github.sadri-dridi
OverviewDiscussionsAdmin

va-w

Volt-amperes to watts, number discarded

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

D1.3/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects, destructive vs. read-only behavior, required permissions, or any operational semantics. The phrase 'number discarded' suggests some data is discarded, but this is opaque and not actionable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short, but this is under-specification rather than concise writing. It conveys almost no information, and the structure fails to front-load any useful content. Every word is wasted because it does not clarify the tool's purpose.

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

Completeness1/5

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

With 10 parameters, zero required, no annotations, and no output schema, the description is severely inadequate. An agent has no way to determine what the tool expects or returns. The description provides almost no assistance for correct invocation, making this definition nearly useless.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

While the schema provides 100% coverage for parameter descriptions, the tool description adds no value in connecting or explaining the parameters. The schema descriptions are individually reasonable (e.g., 'discarded after the shape check'), but the tool description does not explain why a mixture of URL, timezone, JSON, and website parameters are relevant, leaving the overall semantics unclear. With 10 optional params and no guidance, the description fails to compensate for the schema's silence on the tool's overall intent.

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

Purpose1/5

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

The description 'Volt-amperes to watts, number discarded' is cryptic and does not state what the tool actually does. It appears to reference a power conversion, but the input schema contains parameters like URL, city, JSON, path, timezone, and website, which have nothing to do with electrical units. It fails to identify the resource or action, and no sibling differentiation is provided.

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 versus any of its 30+ siblings. The description offers no context, prerequisites, or exclusions, leaving the agent completely in the dark about when this tool is appropriate.

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

All Volt-amperes to watts, number discarded 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