Skip to main content
Glama

Shipfound

by co.shipfound
OverviewDiscussionsAdmin

This workspace

workspace
Read-only

The product this key belongs to: name, URL, plan, credits left, the access summary, tracking state, and the links to the results app and proof page, plus whether the repo you are in is this site's code. Free. Call this first, with repo.

Input Schema

NameRequiredDescriptionDefault
growNotrue when this is the start of grow (the daily routine): Shipfound starts judging today's moves now, so they are ready when you call today.
repoNoThe founder's project you are working in: the output of `git remote get-url origin` there, or the folder name when it has no remote. Credentials in the URL are dropped, never stored.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / grow
      Added value: +{
+  "description": "true when this is the start of grow (the daily routine): Shipfound starts judging today's moves now, so they are ready when you call today.",
+  "type": "boolean"
+}
  2. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / repo
      Added value: +{
+  "description": "The founder's project you are working in: the output of `git remote get-url origin` there, or the folder name when it has no remote. Credentials in the URL are dropped, never stored.",
+  "maxLength": 300,
+  "type": "string"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior. The description adds valuable context: the tool is free, should be called first, and returns specific workspace fields including access summary, tracking state, and whether the current repo matches the site code. It does not explain error behavior or deeper auth details, but with annotations covering safety this is a useful addition.

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

Conciseness4/5

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

The description is compact and front-loads the core resource ('The product this key belongs to'), then lists the fields, then gives the crucial 'Free. Call this first, with `repo`.' It is dense but every phrase corresponds to a returned field or a usage directive.

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 usefully enumerates the return contents so an agent knows what to expect. It also signals the tool is free and first-call. It could do more to explain the 'access summary' or how the tool relates to siblings like access, but it is otherwise complete for a read-only context fetch.

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 both parameters are already fully documented. The description reinforces the `repo` parameter with 'with `repo`' but adds no syntax or meaning beyond the schema, and does not mention the `grow` parameter at all. Baseline 3 is appropriate because the schema carries the parameter semantics.

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

Purpose4/5

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

The description identifies the resource as the workspace/product this key belongs to and enumerates specific returned fields (name, URL, plan, credits, access summary, tracking state, links). It lacks an explicit verb ('returns' or 'gets'), but the retrieval purpose is still clear. It does not directly differentiate from nearby siblings like access or today, though 'Call this first' gives positional clarity.

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 instruction 'Call this first, with `repo`' is an explicit timing and parameter recommendation. It lacks explicit when-not-to-use guidance or named alternatives, but the 'first' directive is a strong usage signal for an entry-point tool.

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