Skip to main content
Glama
Sign In
MIKO MCP Server

MIKO MCP Server

by Miko-Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

MIKO Fact-check

miko.factcheck
Read-only

Verify a factual claim by cross-referencing evidence from multiple providers.

Instructions

Verify a factual claim through MIKO's multi-provider fact-check.

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": {
      "claim": "<claim>"
    },
    "name": "miko.factcheck"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimYesThe claim to verify

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds 'multi-provider' context but does not disclose other behaviors like response format, sources used, or any constraints. With annotations present, the description provides minimal added value.

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 concise sentence with no wasted words, effectively conveying the core purpose.

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

Completeness3/5

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

For a tool with one required parameter and no output schema, the description is minimally adequate. However, it lacks information about the response structure or possible return values, which would help an agent understand the output. Given the simplicity, this is a noticeable gap.

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 coverage is 100% with one parameter 'claim' described as 'The claim to verify'. The description does not add any meaning beyond what the schema provides, so baseline score of 3 is appropriate.

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 states the tool's purpose: 'Verify a factual claim through MIKO's multi-provider fact-check.' This uses a specific verb ('verify') and resource ('claim'), and the tool name includes 'factcheck', distinguishing it from siblings like miko.persona or miko.narrative.

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

Usage Guidelines3/5

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

The description implies usage for verifying claims but provides no explicit guidance on when to use this tool versus alternatives, nor does it mention any limitations or prerequisites. Usage is inferred from the purpose.

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