Skip to main content
Glama

proofite

by com.proofite

Read the daily briefing

get_briefing
Read-only

Read the user's personal AI-written news briefing (daily digest) in full markdown: every story selected today from their newsletters, RSS feeds and monitored web searches, with sources. Returns the latest briefing by default, or a specific one by id or date. Also returns an index of entry ids, needed to rate or correct individual stories.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
briefing_idNoSpecific briefing id (from list_briefings). Omit for the latest.
include_markdownNoInclude the full text. Default true; set false for just the index.

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already indicate readOnlyHint=true (read-only) and no destructive hint. The description adds clarity that the tool returns full markdown and an index, and offers defaults. It does not contradict annotations and provides useful extra behavior context beyond the annotations.

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?

Three sentences cover purpose, scope, and additional use case (index for rating/correction) without any filler. Information is front-loaded and every sentence is necessary.

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?

Given the tool's simplicity (2 optional params, no output schema, low complexity), the description is complete. It explains what the tool returns, how to get different briefings, and links to entry IDs for sibling tools. No missing details for an agent to use it correctly.

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

Parameters4/5

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

The input schema has 100% description coverage for both parameters. The description adds context that 'briefing_id' relates to listing from 'list_briefings' and that omitting it gets the latest, and 'include_markdown' controls text vs index. This adds value beyond the schema alone.

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 reads a personal AI-written news briefing in full markdown. It specifies the content (newsletters, RSS feeds, web searches) and the options to retrieve by id or date, with an index of entry ids for further actions.

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 implies when to use this tool (to read a briefing) and notes the index is needed for rating or correcting stories, which hints at using sibling tools like 'rate_briefing_entry' and 'correct_briefing'. However, it does not explicitly contrast with siblings like 'generate_briefing' or 'list_briefings'.

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