CURRENT SEA - Ambiguity Scan
Explainable ambiguity signals for text. Submitted text is processed but never retained.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"current-sea": {
"url": "https://current-sea.fastapicloud.dev/mcp"
}
}
}Remote endpoints
https://current-sea.fastapicloud.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟢scan_ambiguity(text)
Find wording that may need clarification. Use this when an agent needs an inexpensive, deterministic, explainable check for vague timing, quantities, references, commitments, or standards. The service retains invocation metadata but never the submitted text. Signals are possible issues, not proof of ambiguity.
Input Schema
{
"type": "object",
"properties": {
"text": {
"description": "Text to inspect; it is processed but not retained.",
"maxLength": 10000,
"minLength": 1,
"title": "Text",
"type": "string"
}
},
"required": [
"text"
],
"title": "scan_ambiguityArguments"
}Output Schema
{
"type": "object",
"additionalProperties": true,
"title": "scan_ambiguityDictOutput"
}Community
Evidence