Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

MIME type for a file: find the MIME content type for a file name or extension

mime
Read-only

MIME (content) type for a file name or extension, e.g. report.pdf → application/pdf, and whether browsers usually display it inline. Use when uploading or serving files. Example: file=report.xlsx. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": {
      "file": "<file>"
    },
    "name": "mime"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesFile name or extension

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and non-idempotent, so the safety profile is covered; the description reinforces it ('Reads or computes only and changes nothing') and adds genuinely new context: the cost per call, the free tier, failed calls free, and that repeats are charged (consistent with idempotentHint=false). Since there is no output schema, it also usefully discloses that the result includes the inline-display judgement.

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?

Purpose and example are front-loaded and the mapping example is compact and high-signal. The commercial boilerplate (price, credits key, free tier, failed-call policy) takes roughly half the text, which is necessary but makes the definition longer than the technical content warrants.

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 lookup with no output schema, the description covers what the tool returns (MIME type plus inline-display flag), when to use it, and its cost model. The one notable gap is behavior for unrecognized extensions (error vs. generic fallback like application/octet-stream), which an agent would need to interpret a failed or odd result.

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?

With a single parameter at 100% schema coverage, the baseline is 3. The description restates what the schema already says ('file name or extension') and adds only a worked example (file=report.xlsx); it does not clarify accepted formats beyond that, so it does not materially exceed the schema.

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?

The description names a specific verb+resource ('MIME (content) type for a file name or extension') and backs it with a concrete mapping example (report.pdf -> application/pdf). It also states a secondary output (browser inline-display flag), so an agent knows exactly what it gets back and can distinguish it from siblings like base64_encode or hash.

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?

'Use when uploading or serving files' gives a clear situational trigger, and the file=report.xlsx example shows the call shape. It stops short of naming alternatives or exclusions (e.g., when to prefer a hash or base64 tool), so it lands at clear-context-without-routing rather than full guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.