Skip to main content
Glama

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 ten had what they wanted. seen: the moves shown on the first 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>",
      "answer": "<answer>"
    },
    "name": "grow_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesThe move's key
fromNoWhere the move was when the founder picked it: "first" (the first question), "more" (the next ones), "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. Changed1 schema field changed
    • changedInput schema / properties / from / description
      Previous value: -"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)."New value: +"Where the move was when the founder picked it: \"first\" (the first question), \"more\" (the next ones), \"all\" (the full list), \"typed\" (they named it in their own words)."
  2. 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"
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare that this is a non-destructive write, but the description adds substantive consequences the annotations cannot convey: a 'no' rests the move for 7 days (30 after a second no) so it is not offered again, and 'said' is read by the ranking as the founder's direction from then on. It also notes the call is 'Free,' which carries a quota or pricing implication. It omits any permission or error behavior, which keeps it below a 5.

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 core action is front-loaded in the first clause, and each subsequent sentence carries parameter or consequence information rather than filler. The phrasing is dense and somewhat jargon-heavy (for example, 'which rest like the first screen's'), which costs some readability.

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 does not state what is returned, which is a gap. However, for a five-parameter write tool whose schema already documents most fields, the description covers the action, the source of input, the effect of a 'no', and the downstream use of 'said' and 'seen', which is sufficient to call it correctly.

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%, so the baseline is 3. The description goes further by explaining the purpose of individual parameters: 'from' teaches Shipfound how often the first ten had what they wanted, and 'seen' moves rest like the first screen's. This adds rationale beyond the schema's own field descriptions.

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

Purpose5/5

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

The description opens with a specific verb and resource: 'Record yes or no to a move ... by its key.' It also states the source of the move (today or record_action's next), which distinguishes it from the sibling tools that surface moves. An agent can identify the operation without opening the schema.

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?

It specifies the context in which the tool applies (a move obtained from 'today' or from record_action's next), which gives clear usage context. It does not state explicit exclusions or a when-not-to-use case, so it falls short of a 5.

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.