Skip to main content
Glama

Server Details

Writing studio for novels and screenplays: read your projects and run cited fact-checks.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A3.8/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes: the fact-check pipeline (prepare_factcheck, ground_claim, submit_findings, get_findings) is well delineated, and get_guide vs list_guides is a standard list/get split. The only mild overlap is among the informational tools (get_skarvia_info, list_features, get_pricing), which all serve marketing-style context but remain separable by topic.

Naming Consistency5/5

All ten tools use a consistent snake_case verb_noun pattern (get_*, list_*, ground_claim, prepare_factcheck, submit_findings). The verb choice is predictable and matches the action each tool performs.

Tool Count5/5

Ten tools is well within the sweet spot and each earns its place: four pipeline steps, four info/listing tools, and two guide tools. No obvious filler or redundancy.

Completeness3/5

The fact-check pipeline is coherent, but there are notable gaps: projects are read-only (no create/update/delete), and get_findings requires a check_id with no tool to enumerate existing checks or continuity runs, creating a discovery dead end. Continuity runs are mentioned in descriptions but have no supporting tools.

Available Tools

10 tools
get_findingsA
Read-only
Inspect

Findings for one of the authenticated user's fact-check or continuity runs. Ownership is enforced -- a check_id belonging to another user raises an error rather than leaking their data.

Inputs: check_id (required). Returns: object

get_guideA
Read-only
Inspect

Summary and URL for one guide, looked up by slug.

Call list_guides first to get valid slugs.

Inputs: slug (required). Returns: object

get_pricingB
Read-only
Inspect

Current Storskarvia pricing tiers, features, and monthly fact-check quotas.

Built from config.PLANS, the same list /pricing renders from, so this can no longer drift from the page the way it did while it was kept by hand.

The founder block is read live rather than described in prose. The note here used to say payments "aren't enabled yet" unconditionally, which went on being served after they were switched on, and the tiers listed full price while every human-facing surface offered a founding seat at half of it. An agent asked what Storskarvia costs answered with a price nobody was being charged and omitted the one on offer.

Inputs: no named parameters. Returns: object

get_skarvia_infoB
Read-only
Inspect

What Storskarvia is and how it's positioned.

A professional writing studio for novelists, screenwriters, and video scriptwriters, staffed by an AI team that fact-checks, researches, and tracks continuity -- but never writes the user's prose for them.

Inputs: no named parameters. Returns: object

ground_claimA
Read-only
Inspect

Step 2 of a bring-your-own-agent fact-check. Runs Storskarvia's own server-side retrieval (Wikipedia + searxng) for one claim and returns the sources -- no verdict, no judgment. Your agent should judge the claim ONLY against these returned sources, never outside knowledge. Requires a personal Storskarvia API key as a Bearer token (this is not an open retrieval API).

Inputs: claim (required). Returns: object

list_featuresB
Read-only
Inspect

The AI staff on Storskarvia and what each member actually does.

Source: the "On staff" section of the current landing page.

Inputs: no named parameters. Returns: result

list_guidesA
Read-only
Inspect

Titles, slugs, and URLs of Storskarvia's evergreen craft/how-to guides.

Reads the live GUIDES list straight from app.main (imported lazily -- see the comment on the import below) so this can never drift out of sync with what's actually published at /guides.

Inputs: no named parameters. Returns: result

list_my_projectsA
Read-only
Inspect

The authenticated user's Storskarvia projects (novels, screenplays, video scripts), each with the id, title and binder folder of its documents in binder order. A document id is what prepare_factcheck and submit_findings take. Requires a personal Storskarvia API key as a Bearer token.

Inputs: no named parameters. Returns: result

prepare_factcheckA
Read-only
Inspect

Step 1 of a bring-your-own-agent fact-check. Fetches one of the authenticated user's documents (ownership enforced) plus the exact disclosure and method your agent MUST follow. Requires a personal Storskarvia API key as a Bearer token.

    After this, call ground_claim(claim) once per checkable claim you
    extract from `text`, then submit_findings(...) to store results.
    

Inputs: document_id (required). Returns: object

submit_findingsAInspect

Step 3 of a bring-your-own-agent fact-check. Stores your agent's findings as a real Storskarvia Check, visible on the same findings punch list as a staff-run check. Requires a personal Storskarvia API key as a Bearer token, and ownership of document_id is enforced.

    `disclosure` must be REQUIRED_DISCLOSURE copied verbatim -- proof the
    user was shown it before findings were presented -- or this raises a
    ToolError instead of storing anything. Each item in `findings` must
    have a non-empty quote/explanation, problem in
    {"contradicted","misleading"}, and a non-empty sources list; findings
    missing any of those are rejected wholesale (nothing partial is
    stored).
    

Inputs: findings (required), disclosure (required), document_id (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables writers and AI assistants to take a one-sentence idea through fourteen staged production steps for series, short-form drama, film, or novels, with per-stage criteria checks that flag missing or contradictory material. It also provides project scaffolding, continuity ledgers, outline and screenplay drafting, storyboards, version rollback, and Word/portfolio export through 54 local-only tools.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to draft long-form web novels with persistent, disk-backed memory, assembling a pre-writing task brief from structured settings, outlines, foreshadowing ledgers, and timelines, then committing post-chapter fact increments. It also audits pacing, checks per-chapter six-dimension consistency, gates commits on unresolved review findings, and can replay the commit chain to rebuild state when records and manuscripts disagree.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI-driven long-form novel creation and management, including chapter generation, character and timeline tracking, semantic memory retrieval, version savepoints, and deep consistency checking across multiple projects through MCP tools, with support for local LM Studio or any OpenAI-compatible API.
      16
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources