Skip to main content
Glama
Sign In
Anti-Bullshit MCP Server

Anti-Bullshit MCP Server

by bmorphism
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

analyze_claim

Evaluate claims using empirical, responsible, harmonic, or pluralistic frameworks to identify validation steps and ensure credible information.

Instructions

Analyze a claim using multiple epistemological frameworks and suggest validation steps

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": {
      "text": "<text>"
    },
    "name": "analyze_claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
frameworkNoValidation framework to use (empirical, responsible, harmonic, or pluralistic)
textYesClaim to analyze

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'analyze' and 'suggest validation steps' but doesn't specify what the analysis entails (e.g., output format, depth), whether it's read-only or has side effects, or any constraints like rate limits or authentication needs. This leaves significant gaps for a tool with no annotation coverage.

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?

The description is a single, efficient sentence that front-loads the core purpose ('analyze a claim') and adds key details ('using multiple epistemological frameworks and suggest validation steps'). Every word contributes meaning without redundancy or waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of analyzing claims with frameworks and no annotations or output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., analysis results, validation steps list), how frameworks differ, or behavioral aspects like safety or performance. For a tool with 2 parameters and no structured output, more context is needed.

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 the schema already documents both parameters ('framework' with enum values and 'text' as the claim). The description adds no additional semantic context beyond what's in the schema, such as explaining the frameworks or how they affect analysis. Baseline 3 is appropriate when the schema handles parameter documentation.

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 clearly states the action ('analyze') and resource ('a claim'), specifying it uses 'multiple epistemological frameworks' and 'suggest validation steps'. This provides a specific verb+resource combination, though it doesn't explicitly differentiate from sibling tools like 'check_manipulation' or 'validate_sources' which might have overlapping domains.

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?

The description provides no guidance on when to use this tool versus alternatives like 'check_manipulation' or 'validate_sources'. It mentions 'validation steps' but doesn't clarify if this is for preliminary analysis, in-depth validation, or specific contexts. No exclusions or prerequisites are stated.

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

Deploy Server

Other Tools

Related Tools