list_family_almanac_feedsList The Family Almanac's free machine-readable feeds and their MCP/REST availability. OpenAPI is also published at https://thefamilyalmanac.com/openapi.json.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| feeds | Yes | ||
| contract | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "contract": {
+ "type": "string"
+ },
+ "count": {
+ "type": "number"
+ },
+ "feeds": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "auth": {
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "mcpTool": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "method": {
+ "type": "string"
+ },
+ "path": {
+ "type": "string"
+ },
+ "rest": {
+ "type": "string"
+ },
+ "summary": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "method",
+ "path",
+ "summary",
+ "mcpTool",
+ "rest",
+ "auth"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "contract",
+ "count",
+ "feeds"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context beyond annotations by noting the feeds are free, machine-readable, and that an OpenAPI document is published at a specific URL. This enriches the agent's understanding without repeating 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences carry the entire definition with no wasted words. The core listing purpose is front-loaded, and the supplementary OpenAPI reference is placed second. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter, read-only listing tool with an output schema and annotations, the description covers what the tool lists and points to the OpenAPI spec for further detail. Nothing needed to invoke the tool correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so there is no parameter meaning for the description to add. Baseline for a zero-parameter tool is 4, and the description appropriately spends no effort on parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('List'), a resource ('The Family Almanac's free machine-readable feeds'), and the distinguishing dimension ('their MCP/REST availability'). It clearly separates this tool from the sibling get/search tools, which are content-retrieval operations.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear context: use this tool to discover available machine-readable feeds and their MCP/REST availability. It does not explicitly name exclusions or an alternative, but the purpose is distinct enough from the sibling retrieval tools that an agent can infer when it applies.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.