Skip to main content
Glama

Shipfound

by co.shipfound
OverviewDiscussionsAdmin

Today

today

What /shipfound:grow shows: what happened since the founder's last session (AI visits, AI crawler hits, conversions, what got verified or failed), what is due (tests with a verdict, shipped work to verify), the one move to offer, the next four (after), every other move with work behind it (more), and every other kind of move Shipfound makes (catalog, with ready false and what it needs when something comes first), so a founder can reach any of it. focus is what holds the product back this week, read from its numbers, and the five moves go after it. bet is the week's goal and bet with its check day; take is Shipfound's own view of the week, which may disagree with the founder (disagrees); calls is what came of the founder's own calls over its first pick; question is today's one question, when an answer would change the plan; happened carries the verdicts on shipped work as they are read. Each move's why is the reason to do it for this product today, chosen and written over the founder's own results, the people who asked, the peer study and the play library (what it does is in does when why is that reason); gets is who it reaches and the first sign to watch for; then is what it leads to once its own work is done; rests is what it rests on in one line. It looks first, from stored data: a move is offered only when there is concrete work behind it (checks still failing on the live site, directories not listed yet, the page worth writing with its volume), and not the same move two days running. Logs the offer. 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 each does for the person using the product, the problem it solves when the code or PR says, and the PR link. Lets today offer a post or an X Article about one.
repoCommitsNoCommits to the founder's product in the last 7 days, read from their repo, leaving out Shipfound's own PRs (branches named shipfound/...). Lets today offer a build in public note on the week's work. Leave out when there is no repo.

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 each does for the person using the product, the problem it solves when the code or PR says, and the PR link. Lets today offer a post or an X Article about one.",
+  "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. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / repoCommits
      Added value: +{
+  "description": "Commits to the founder's product in the last 7 days, read from their repo, leaving out Shipfound's own PRs (branches named shipfound/...). Lets today offer a build in public note on the week's work. Leave out when there is no repo.",
+  "maximum": 100000,
+  "minimum": 0,
+  "type": "integer"
+}
  3. First observed

TDQS

C2.4/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=false, openWorldHint=false, and destructiveHint=false, and the description is consistent with those. It adds some useful behavioral context—stored-data lookup, offer logging, deduplication ('not the same move two days running'), and being free—but these details are buried and it does not discuss permissions or side-effect specifics.

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

Conciseness2/5

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

The description is an extremely long run-on paragraph with nested parentheticals and undefined terms, so it is not front-loaded or easy to scan. It is over-specified in content but poorly structured, causing important points to be buried.

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

Completeness2/5

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

There is no output schema, so the description must carry the burden of explaining return shape. It attempts to enumerate output fields, but the presentation is too tangled and jargon-heavy to give an agent a clear, complete model of what to expect.

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 coverage is 100%, so the two optional parameters are fully documented by the schema. The main description does not mention 'features' or 'repoCommits' or add meaning beyond the schema, so baseline 3 is appropriate.

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

Purpose2/5

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

The description starts with 'What /shipfound:grow shows' and then enumerates many dashboard fields, but it never states a clear verb and resource such as 'returns today's growth dashboard' or distinguishes the tool from its many siblings. The purpose is buried in a dense content inventory rather than stated directly.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only contextual clue is 'Free,' which does not help an agent choose among the large set of sibling tools.

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