Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

emoji_list

Search emoji by name or keyword and return the character, shortcode and category. Pure CPU, instant.

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": {
      "q": "<q>"
    },
    "name": "emoji_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesKeyword such as rocket
limitNoMax results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed3 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results",
+  "type": "integer"
+}
    • addedInput schema / properties / q
      Added value: +{
+  "description": "Keyword such as rocket",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "q"
+]
  4. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the operation is non-mutating search and the cost profile is "Pure CPU, instant" (no network/external calls). It does not state the default or maximum for limit, whether results are ranked, or how zero matches are returned, which are the remaining behavioral gaps.

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

Conciseness5/5

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

Two short sentences that front-load what the tool does and then add the return shape and cost profile. No filler, no restatement of the tool name as a title.

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

Completeness4/5

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

For a two-parameter lookup with a fully described schema and no output schema, the description supplies the one thing the schema can't: what fields come back. Slightly incomplete in that it omits the default value of limit and the behavior on no matches.

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 both parameters are already documented ("Keyword such as rocket", "Max results") and the baseline of 3 applies. The description's phrasing "by name or keyword" hints that the query matches names as well as keywords, but adds no further syntax or matching-rule detail.

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

Purpose5/5

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

Specific verb plus resource ("Search emoji by name or keyword") and it names the exact return shape: character, shortcode, category. No sibling in the list does emoji lookup, so an agent can route to it without ambiguity.

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

Usage Guidelines3/5

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

Usage is implied by "Search emoji by name or keyword", and the schema example ("Keyword such as rocket") reinforces the query form. However, there is no explicit when-to-use framing, no note on what to expect for a miss (empty list vs error), and no limits on the broadness of the query.

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