Skip to main content
Glama

proofite

by com.proofite

Import an OPML subscription file

import_opml
Idempotent

Import subscriptions from another RSS reader (Feedly, Inoreader, FreshRSS, NetNewsWire) by passing the OPML file contents. Set dry_run true first to see what is in it and what is already present; then run it for real to add them (they are validated one by one, and the ones that fail come back with the reason).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
opmlYesThe full OPML/XML file contents
limitNoMax feeds to add in this call (default 20 — big imports go in batches)
dry_runNotrue = only list what would be imported
source_idYesWhich inbox to import into

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds critical behavioral context: the batch process validates feeds one by one and returns failures with reasons. It also reveals the dry-run pattern, which is vital for agent decision-making. Without annotations, this would be a 5, but the annotation burden reduces the score slightly.

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?

Two sentences, no wasted words. The first sentence states the what and who (supported sources). The second covers the workflow and edge cases. Every sentence serves a distinct purpose.

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

Completeness5/5

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

Despite lacking an output schema, the description tells the agent what to expect (failures with reasons) and how to use the tool correctly (dry-run first, batch processing). The sibling list shows many tools for feed management, and this description equips the agent to choose this for bulk OPML imports without confusion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, meaning all 4 parameters have schema descriptions. The tool description adds value beyond the schema by explaining the workflow (dry_run usage) and the consequence of the limit parameter ('big imports go in batches'). This surpasses the baseline 3 for high coverage.

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 uses specific verbs ('Import subscriptions') and identifies the exact resources (OPML file) and common sources (Feedly, Inoreader, etc.). It clearly distinguishes from siblings like add_feed (single feed) and add_web_search, making the tool's purpose unmistakable.

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

Usage Guidelines4/5

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

The description provides explicit guidance on the workflow: first set dry_run true to preview, then run for real. It also mentions validation behavior and error reporting. However, it doesn't explicitly contrast with siblings like create_source or discover_sources, leaving some ambiguity about when to use this vs. alternative bulk operations.

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

All proofite toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools target distinct operations (e.g., add_feed vs. remove_feed, get_source vs. list_sources). However, there is some ambiguity between correct_briefing and tune_topic (both adjust content based on user feedback) and between request_deep_dive and correct_briefing (both can trigger deeper investigation). The descriptions help, but an agent could misselect.

Naming Consistency5/5

Tool names follow a very consistent verb_noun pattern (e.g., add_feed, create_source, generate_briefing, list_sources). All use snake_case with clear, descriptive verbs and nouns. No mixing of conventions.

Tool Count4/5

With 27 tools, the server covers a rich domain of news feed management, briefing generation, and user preferences. This is slightly above the typical sweet spot but still reasonable given the complexity. Each tool serves a distinct purpose; the count is justified.

Completeness5/5

The tool set provides full lifecycle coverage: sources can be created, read, updated, and deleted; feeds and searches can be added and removed; briefings can be generated, listed, read, rated, and corrected; deep dives and read-later items are supported. There are no obvious gaps—the domain is thoroughly covered.

Resources