Skip to main content
Glama

Shipfound

by co.shipfound.api
OverviewDiscussionsAdmin

Build in public notes: what to write about

notes_context
Read-only

What a build in public note can be about (a milestone from the site's hard goals, a launch, a feature shipped, a free tool live, a skill published, this week's commits when repoCommits is passed), each source written once; which platforms are open (X every 3 days, Reddit every 14, by the audit); the flagship X Article (article: open every 14 days, whether the account has X Premium, format article or thread without Premium, and the sources it can be about); the founder's voice per platform if learned; and the subreddits that take these posts, with their rules. Free.

Input Schema

NameRequiredDescriptionDefault
featuresNoFeatures the founder shipped in the last 14 days, read from the repo (merged PRs, feat: commits), leaving out Shipfound's own PRs: what it does for the person using the product, the problem it solves when the code or PR says, and the PR link
repoCommitsNoCommits to the product in the last 7 days, leaving out Shipfound's own PRs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / features
      Added value: +{
+  "description": "Features the founder shipped in the last 14 days, read from the repo (merged PRs, feat: commits), leaving out Shipfound's own PRs: what it does for the person using the product, the problem it solves when the code or PR says, and the PR link",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "problem": {
+        "maxLength": 300,
+        "type": "string"
+      },
+      "title": {
+        "maxLength": 160,
+        "minLength": 3,
+        "type": "string"
+      },
+      "url": {
+        "maxLength": 500,
+        "type": "string"
+      }
+    },
+    "required": [
+      "title"
+    ],
+    "type": "object"
+  },
+  "maxItems": 5,
+  "type": "array"
+}
  2. Added

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavioral context: cadence gates ('X every 3 days, Reddit every 14'), a 14-day article window, X Premium gating, per-source write-once semantics, and the cost ('Free'). These are non-obvious constraints that change how an agent should act.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It opens with the purpose, and most clauses carry genuine information (necessary given there is no output schema), but it is a single sprawling sentence with nested parentheticals that is hard to skim or parse.

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

Completeness4/5

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

With no output schema, the description must describe the return payload, and it does so thoroughly — sources, open platforms with cadence, article rules and format gating, learned voice, and target subreddits with rules. For a two-parameter read tool with read-only annotations, this is close to complete; only explicit routing to sibling tools is missing.

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 description coverage is 100%, so the schema already documents both parameters and baseline is 3. The description does add one linkage by noting the commits source is active 'when repoCommits is passed', but it says nothing beyond the schema about the features array shape or limits.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the contents a build-in-public note can draw on (milestones, launches, shipped features, free tools, skills, commits) but never states the verb plainly — it reads as a content dump rather than 'returns the inputs you need to decide what to write about.' No sibling is named, so an agent must infer the difference between this, notes_save, and notes_voice from the name alone.

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?

Conditions are embedded in parentheticals — 'this week's commits when repoCommits is passed', 'format article or thread without Premium' — which implies when certain sources apply. But there is no explicit when-to-use-this-vs-alternatives guidance and no stated prerequisite for calling it before notes_save.

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

All Shipfound toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources