Skip to main content
Glama

Grains to grams, number discarded

by io.github.sadri-dridi
OverviewDiscussionsAdmin

grain-g

Grains to grams, 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 disclosing behavioral traits. The description discloses nothing about side effects, discard semantics, permissions, or output characteristics. The phrase 'number discarded' hints at some action but without context or connection to the schema it provides no usable transparency.

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

Conciseness1/5

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

The description is short but not concise—it is under-specified. The two phrases 'Grains to grams' and 'number discarded' do not form a coherent tool description and fail to earn their place, because they convey no useful information.

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?

Given the tool has 10 heterogeneous parameters, no annotations, and no output schema, the description is completely inadequate. An agent has no idea what operation the tool performs, what inputs are expected, or what 'number discarded' refers to.

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%, and each parameter already has its own meaningful description (e.g., 'ref: Git ref name; discarded after the shape check'). The tool description adds nothing to parameter meaning, but per the rubric the baseline is 3 when schema coverage is high, even if the description contributes nothing.

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 'Grains to grams, number discarded' appears to be a nonsensical or placeholder phrase that does not describe any tool operation. It gives no verb, resource, or scope, and it actively misleads by suggesting a unit conversion when the input schema contains a wide array of unrelated string parameters (url, city, feed, json, path, zone, etc.).

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 whatsoever about when to use this tool or when to prefer a sibling. With 30 sibling tools, the absence of any usage direction leaves the agent completely unable to route correctly.

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

All Grains to grams, 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