Skip to main content
Glama

Shipfound

by co.shipfound.api
OverviewDiscussionsAdmin

The founder's answer to a move

grow_answer

Record yes or no to a move from today or record_action's next, by its key. A no rests the move for 7 days (30 after a second no), so it is not offered again tomorrow. For a yes, from says where the founder found it, so Shipfound learns how often the first three had what they wanted. seen: the moves shown on the next-five screen and not picked, which rest like the first screen's. said: what the founder typed in their own words instead of picking, word for word; Shipfound's ranking reads it as their direction from then on. Free.

Input Schema

NameRequiredDescriptionDefault
keyYesThe move's key
fromNoWhere the move was when the founder picked it: "first" (the first question), "more" (the next five), "all" (the full list), "typed" (they named it in their own words).
saidNoThe founder's own words when they typed an answer instead of picking, as they wrote them.
seenNoKeys of the moves printed on the next-five screen that the founder did not pick.
answerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Where the move was when the founder picked it: \"first\" (the first question), \"more\" (the next five), \"all\" (the full list), \"typed\" (they named it in their own words).",
+  "enum": [
+    "first",
+    "more",
+    "all",
+    "typed"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / said
      Added value: +{
+  "description": "The founder's own words when they typed an answer instead of picking, as they wrote them.",
+  "maxLength": 1000,
+  "type": "string"
+}
    • addedInput schema / properties / seen
      Added value: +{
+  "description": "Keys of the moves printed on the next-five screen that the founder did not pick.",
+  "items": {
+    "maxLength": 2000,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 10,
+  "type": "array"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing state effects: a no rests the move for 7 days, 30 after a second no; 'seen' keys rest like the first screen's; 'said' text becomes the ranking's direction going forward. This is exactly the kind of downstream consequence an agent needs and annotations cannot convey.

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?

Front-loads the core action and each subsequent clause carries information about a distinct parameter or consequence. The trailing 'Free.' is wasted marketing text and the sentences are dense, but overall there is little filler.

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?

No output schema exists, so the description should ideally hint at the response, which it does not. However, it fully covers the input semantics and the resulting state changes for a 5-parameter mutation tool, leaving only return-value shape unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 80%, and the description adds genuine meaning on top: what 'from' is used for (learning how often the first three had what they wanted), what 'seen' captures and its resting effect, and how 'said' is consumed verbatim. 'key' and 'answer' remain schema-only, which is acceptable.

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?

States a specific verb+resource ('Record yes or no to a move') and anchors the input source by naming siblings ('from today or record_action's next'). The domain term 'move' is slightly jargon-heavy but the surrounding text makes the operation unambiguous.

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?

Clearly frames the call as the follow-up to showing moves ('today' / 'record_action's next'), and explains the distinction between a yes and a no path. It lacks an explicit 'do not use this if...' exclusion, but the context of use is clear.

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