Skip to main content
Glama

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 nine (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. Each move carries channel (paid, seo, aso, social, outreach, conversion or basics), and channels gives each label in display order, so the moves can be shown grouped. focus is what holds the product back this week, read from its numbers, and the ten 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "today"
  }
}

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.7/5.0
Behavior3/5

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

Annotations are sparse but not contradicted: readOnlyHint=false is consistent with 'Logs the offer', so this is a read that also records state. The description adds real behavioral value beyond that — data is read from stored data, an offer is suppressed unless concrete work backs it, and the same move is not re-offered two days running. However this is buried inside a dense field-by-field catalog rather than stated up front, and side effects are only hinted at with 'Logs the offer'.

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?

A single run-on paragraph of chained clauses separated by commas and semicolons, with nested parentheticals ('catalog, with ready false and what it needs when something comes first'). Field definitions are not front-loaded or scannable, and the key operating rule (looks first, logs the offer, free) arrives only at the very end. Much content is needed given no output schema, but the structure works against comprehension.

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

Completeness3/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 carry return-value semantics, and it does enumerate most fields. But it omits any explanation of how the two input parameters (features, repoCommits) affect the result, gives no sense of size/shape of the response, and never states when to call it versus siblings. Adequate but with clear gaps for a tool this complex.

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% and the two optional parameters (features, repoCommits) are documented in detail in the schema itself. The description never mentions either input parameter, so it adds no meaning beyond the schema; the baseline of 3 applies.

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 opens with 'What /shipfound:grow shows' and then enumerates payload fields (happened, due, the one move to offer, next nine, catalog), so an agent can infer this returns a daily briefing/offer. But it never states a clean verb+resource ('Returns today's briefing for the founder'), and jargon like 'move', 'focus', 'bet', 'take', 'calls' is used before being defined. It does not distinguish itself from siblings such as plan, shipped or verify.

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 when-to-use guidance and no named alternative. The closest thing is the internal gating rule ('a move is offered only when there is concrete work behind it ... and not the same move two days running'), which explains how the offer is produced, not when an agent should call this tool versus plan or verify. 'Free' is a cost hint, not usage guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.