Skip to main content
Glama
Sign In

GadgetHumans API Hub

by com.gadgethumans
OverviewDiscussionsAdmin

mime_types

List common MIME types by category with their usual file extensions. 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": {
      "category": "<category>"
    },
    "name": "mime_types"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesimage, text, application, audio or video

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed2 schema fields changed
    • addedInput schema / properties / category
      Added value: +{
+  "description": "image, text, application, audio or video",
+  "type": "string"
+}
    • addedInput schema / required
      Added value: +[
+  "category"
+]
  4. Added

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description does carry the burden, and it partially meets it by disclosing "Pure CPU, instant", which tells the agent there is no network call, no cost and no side effects. It does not explicitly state read-only behavior or describe the shape of the returned list, but for a trivial static-data tool this is adequate rather than rich.

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 with zero waste; the purpose is front-loaded and the cost characteristic follows immediately. Nothing could be removed without losing information.

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 one-parameter, no-output-schema, static-data tool this covers what an agent needs: what is returned (types plus extensions), how it is scoped (category), and its cost profile. The only real omission is routing against the mime_lookup sibling.

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 the single category parameter already enumerates the accepted values (image, text, application, audio or video). The description adds only the phrase "by category", which restates the schema, so baseline 3 applies.

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?

States a specific verb and resource ("List common MIME types by category with their usual file extensions"), so the agent knows exactly what comes back. It does not differentiate itself from the sibling mime_lookup, which is presumably a single-type lookup, so the boundary between the two is left implicit.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of the closely related mime_lookup sibling, which is the natural alternative. Usage is only implied by the word "List", leaving the agent to infer that this tool is for browsing a category rather than resolving one specific type.

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