Skip to main content
Glama
Sign In

MentionFox

by io.github.OsakaSaul
OverviewDiscussionsAdmin

Your recent research history

get_my_recent_research
Read-onlyIdempotent

What you have already looked up. Free: nothing is charged. Lists the people you have researched, the write-ups you have had made, and the calls you have run here recently — yours only, nobody else's. Worth calling before you pay for something: if you looked this person up last month, you already have it. Use it for "have I checked this person before", "what did I look at last week", "show me what I have". Nothing is looked up and nothing is charged. Plans and credits: https://mentionfox.com/pricing

Input Schema

NameRequiredDescriptionDefault
limitNoHow many items of each kind to list, 1 to 50. Default 10.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call could not do the work; says why and that nothing was charged where that is so.
messageNoA plain note about the answer, for example why candidates were returned instead of a result.
summaryNoWhat you have, in a sentence.
pricing_noteNoWhat this call cost and what a repeat costs.
dossier_countNoHow many full files you have.
profile_countNoHow many people you have looked up.
credits_chargedNoCredits this call took. 0 when nothing was charged.
recent_dossiersNoYour most recent full files.
recent_profilesNoThe people you looked up most recently.
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.
recent_connector_invocationsNoYour most recent calls to these tools.

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. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"How many items of each kind to list, 1 to 50. Default 10."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "credits_charged": {
+      "description": "Credits this call took. 0 when nothing was charged.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "dossier_count": {
+      "description": "How many full files you have.",
+      "type": [
+        "number",
+        "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"
+      ]
+    },
+    "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"
+      ]
+    },
+    "profile_count": {
+      "description": "How many people you have looked up.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "recent_connector_invocations": {
+      "description": "Your most recent calls to these tools.",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "recent_dossiers": {
+      "description": "Your most recent full files.",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "recent_profiles": {
+      "description": "The people you looked up most recently.",
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "summary": {
+      "description": "What you have, in a sentence.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "title": "Your recent research",
+  "type": "object"
+}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only and non-destructive annotations, it discloses that the operation is free, performs no new lookup, and exposes only the current user's history. These billing, execution, and data-scope details are directly useful when deciding whether invocation is safe and appropriate.

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

Conciseness3/5

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

The purpose is front-loaded and the examples are easy to scan, but the definition repeats the free/no-charge point and ends with a pricing link that is unnecessary for tool selection or invocation. It is clear but noticeably more verbose than needed.

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?

Together with the complete parameter schema, annotations, and output schema, the description supplies nearly everything needed to invoke this simple zero-required-parameter tool correctly. It could be more complete by defining what 'recently' means or explicitly directing agents to a sibling when they need fresh research or full report contents.

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?

The sole limit parameter already has complete schema documentation, including its range, default, and per-category behavior. The description adds no further parameter semantics, so the high schema coverage supports the baseline score.

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 clearly identifies a history-listing operation covering researched people, requested write-ups, and previous calls, restricted to the current user. Emphasizing what was already looked up distinguishes it from siblings that perform fresh enrichment, scans, or report retrieval.

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 an explicit decision point—call this before paying for research that may already exist—and supplies three concrete natural-language use cases. The statement that nothing new is looked up also helps prevent using it as a substitute for fresh-research tools.

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