Skip to main content
Glama
Sign In

MentionFox

by io.github.OsakaSaul
OverviewDiscussionsAdmin

Make a sendable file

export_report
Destructive

Turn something you already have into a file you can send someone: a web page, a print-ready page you can save as a PDF, or plain text. Nothing about MentionFox appears on it, and you can put your own name, logo and colours on it, so it goes to a client as your work. Use it for "send me that as a PDF", "I need this as a document for the client", "put our branding on it". This makes a fixed copy of what exists now — for something that keeps up to date as the information changes, share the live link instead. Costs 5 credits. Plans and credits: https://mentionfox.com/pricing

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": {
      "report_type": "<report_type>",
      "report_id": "<report_id>"
    },
    "name": "export_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNohtml: a web page. pdf: a print-ready page to save as a PDF. markdown: plain text. Default html.html
brandingNoOptional. Your own branding on the file, so it goes out as your work.
report_idYesWhich one. For a dossier, the person id from get_dossier (person_profile_id). For a compare, the names separated by commas, for example "Ada Lovelace, Alan Turing". For the others, the id the earlier result gave.
report_typeYesWhat to turn into a file: dossier (the file on one person), compare (a side-by-side), or one of the evaluation types.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call could not do the work; says why and that nothing was charged where that is so.
titleNoThe file's title.
formatNohtml, pdf or markdown.
contentNoThe file itself (the page or the text).
messageNoA plain note about the answer, for example why candidates were returned instead of a result.
summaryNoWhat the file contains.
report_typeNoWhat was turned into a file.
download_urlNoA link to download the file.
pricing_noteNoWhat this call cost and what a repeat costs.
credits_chargedNoCredits this call took. 0 when nothing was charged.
file_size_bytesNoSize of the file.
mentionfox_checkNoPresent when the call named a company MentionFox holds a record for: MentionFox's own check on it (the sentence, red flags and notes with their source links, how many sources) and a link to the full findings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / mentionfox_check
      Added value: +{
+  "description": "Present when the call named a company MentionFox holds a record for: MentionFox's own check on it (the sentence, red flags and notes with their source links, how many sources) and a link to the full findings."
+}
  2. Changed11 schema fields changed
    • changedInput schema / properties / branding / description
      Previous value: -"Optional white-label branding override"New value: +"Optional. Your own branding on the file, so it goes out as your work."
    • addedInput schema / properties / branding / properties / company_name / description
      Added value: +"Your company name, shown in the header."
    • addedInput schema / properties / branding / properties / font_family / description
      Added value: +"A font name, for example Inter."
    • addedInput schema / properties / branding / properties / footer_text / description
      Added value: +"A line for the footer, for example your address or a disclaimer."
    • addedInput schema / properties / branding / properties / logo_url / description
      Added value: +"A link to your logo image, for example https://example.com/logo.png."
    • addedInput schema / properties / branding / properties / primary_color / description
      Added value: +"Main colour as a hex code, for example #0F172A."
    • addedInput schema / properties / branding / properties / secondary_color / description
      Added value: +"Accent colour as a hex code, for example #F27A3A."
    • addedInput schema / properties / format / description
      Added value: +"html: a web page. pdf: a print-ready page to save as a PDF. markdown: plain text. Default html."
    • changedInput schema / properties / report_id / description
      Previous value: -"For dossier: person_profile_id. For compare: comma-separated names. For others: the eval/report row id."New value: +"Which one. For a dossier, the person id from get_dossier (person_profile_id). For a compare, the names separated by commas, for example \"Ada Lovelace, Alan Turing\". For the others, the id the earlier result gave."
    • addedInput schema / properties / report_type / description
      Added value: +"What to turn into a file: dossier (the file on one person), compare (a side-by-side), or one of the evaluation types."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "content": {
+      "description": "The file itself (the page or the text).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "credits_charged": {
+      "description": "Credits this call took. 0 when nothing was charged.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "download_url": {
+      "description": "A link to download the file.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Present when the call could not do the work; says why and that nothing was charged where that is so.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "file_size_bytes": {
+      "description": "Size of the file.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "format": {
+      "description": "html, pdf or markdown.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A plain note about the answer, for example why candidates were returned instead of a result.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "pricing_note": {
+      "description": "What this call cost and what a repeat costs.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "report_type": {
+      "description": "What was turned into a file.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "summary": {
+      "description": "What the file contains.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "The file's title.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "A sendable file",
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare the mutation/non-idempotent profile; the description adds the behavior that actually matters — each call produces a frozen snapshot rather than a live artifact, costs 5 credits, strips MentionFox branding, and supports custom logo/colours. It does not state whether a failed or repeated call still burns credits, which is the main open risk given idempotentHint=false.

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?

Front-loaded with what the tool produces, then the snapshot-vs-live caveat, then cost. The example utterances and pricing URL are slightly padding, but each sentence carries usable signal and nothing is repeated.

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 4-parameter export tool with a full output schema and rich annotations, the description covers the dimensions an agent needs: output formats, branding scope, snapshot semantics, and cost. Minor gaps remain — the report_id cross-references to get_dossier are documented in the schema rather than the description, and error behavior is unaddressed.

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 every parameter including the nested branding object and both enums is already documented in the schema. The description adds no format or report_id nuance beyond what the schema says, so the 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?

The description names a specific action and output: converts an existing report into a sendable file in html/pdf/markdown, with branding applied and no MentionFox watermark. The vague opener 'something you already have' is resolved by the schema's report_type enum, but the description itself never names the report kinds it accepts, so the agent must open the schema to know what 'something' means.

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

Usage Guidelines5/5

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

It gives explicit trigger phrases ('send me that as a PDF', 'put our branding on it') and, critically, an explicit when-not: for anything that must stay current, share the live link instead of making a fixed copy. The 5-credit cost and pricing link let the agent weigh the call against a cheaper alternative.

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

All MentionFox 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