Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

changed

Change detection for polling agents: pass the hash you saw last time and get changed:true/false back instead of re-reading and diffing the whole payload yoursel

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": {
      "check": "<check>"
    },
    "name": "changed"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkYesWhat to watch: token (safety verdict), price (USD price), dns (DNS records plus HTTP status) or gas (gas price). Default token.
sinceNoThe hash returned by your previous call. Omit on the first call.
targetNoContract address (check=token|price), domain (check=dns) or chain (check=gas, default base)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavior burden. It does disclose the core contract (hash in, boolean out) and the efficiency motivation, but omits the response shape beyond the boolean — notably whether a new hash is returned for the next poll — and says nothing about rate limits, caching, or error behavior on a stale hash.

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?

Single sentence, front-loaded with the tool's role and value proposition, with no filler. The only blemish is the truncated final word ('yoursel'), which is a quality issue rather than a structural one.

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?

The tool is simple (3 params, full schema coverage, no output schema), so most burden is already met. However, the round-trip contract — that the caller must store and resend the hash returned by each call — is only implied across the description and `since` schema text, not stated as a whole; an agent could call it correctly but might not know to persist the new hash.

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 coverage is 100%, so all three parameters are documented in the schema, establishing the baseline of 3. The description reinforces the `since` parameter's meaning ('the hash you saw last time') but adds no syntax, format, or hash-algorithm detail beyond what the schema already states.

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 description names a specific capability — hash-based change detection that returns changed:true/false — and frames it around polling agents, which is concrete. It does not name a sibling to contrast with (e.g. hash_compare or diff), so differentiation is left to inference, but the verb+resource is clear.

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

Usage Guidelines4/5

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

It states the calling context (polling agents) and the usage pattern: pass the hash from the previous call rather than re-reading the payload. When-not guidance is implicit ('instead of re-reading and diffing the whole payload yourself'), and no alternative tool is explicitly named, which keeps it short of a 5.

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

All GadgetHumans API Hub 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