Skip to main content
Glama
Sign In

hunchful

by io.hunchful
OverviewDiscussionsAdmin

Plans: gather the gang (Samla gänget)

create_plan

"Få ihop gänget på fredag": a meetup with 1–9 time and place options, to ONE of their gangs (whoami lists them) or friends by name. People vote, "most can" decides the evening before. It's a card they tap in Hem: nothing is sent until then. Ask them what and where first; never invent a place or a person.

Input Schema

NameRequiredDescriptionDefault
gangNoA gang's name. Or friends.
titleYesShort, e.g. "Padel".
friendsNoFriends by name or @handle.
optionsYes
activityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / activity / description
      Removed value: -"One or two words, e.g. film, fika, walk."
    • changedInput schema / properties / gang / description
      Previous value: -"A gang the person is in (name). Use this OR friends."New value: +"A gang's name. Or friends."
    • removedInput schema / properties / options / description
      Removed value: -"1–9 time+place options."
    • removedInput schema / properties / options / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / options / items / properties / place / description
      Previous value: -"A real, named place, e.g. \"Filmstaden Bergakungen\"."New value: +"A real, named place."
    • changedInput schema / properties / options / items / properties / when / description
      Previous value: -"ISO 8601 with offset, e.g. 2026-10-06T18:00:00+02:00 (use the person's own UTC offset — list_plans says which time zone)."New value: +"ISO 8601 with their UTC offset, e.g. 2026-11-06T18:00:00+01:00 (waiting_for_me has their time zone)."
    • changedInput schema / properties / title / description
      Previous value: -"What you're doing, short: \"Bio\", \"Fika på Espresso House\", \"Padel\"."New value: +"Short, e.g. \"Padel\"."
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "itemId": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "note": {
-      "type": "string"
-    },
-    "options": {
-      "items": {
-        "additionalProperties": false,
-        "properties": {
-          "place": {
-            "type": "string"
-          },
-          "when": {
-            "type": "string"
-          },
-          "whenText": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "when",
-          "whenText",
-          "place"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "planId": {
-      "type": "string"
-    },
-    "shareUrl": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status": {
-      "enum": [
-        "sent",
-        "draft"
-      ],
-      "type": "string"
-    },
-    "url": {
-      "type": "string"
-    },
-    "who": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "status",
-    "who",
-    "options",
-    "note"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write is known to be non-destructive and closed-world. The description adds genuinely useful behavior beyond that: the 1–9 option cap (absent from the schema), the voting rule, and the fact that nothing is delivered until the card is tapped. It still omits what the caller gets back on creation and any permission or error conditions, keeping it below the top band.

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-loaded with the concrete scenario and the core constraint, then the delivery behavior, then the safety instruction. The opening Swedish quote is flavor but does convey the use case; a few phrases could be tightened without loss.

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?

For a five-parameter creation tool with a nested options array and no output schema, the description covers the mechanics an agent needs: option limits, targeting, voting, and the deferral of sending. Only the return value and the meaning of 'activity' are left 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 60%, and the description compensates well: it clarifies that options are time-and-place pairs, that gang and friends are alternative targeting modes with whoami as the lookup, and that place must be a real named place rather than invented. The 'activity' parameter remains undefined in both schema and description, which is the remaining gap.

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?

States a specific verb and resource (create a meetup plan with 1–9 time/place options), names the audience (one gang from whoami, or friends by name), and describes the outcome (people vote, 'most can' decides the evening before). An agent can tell this apart from create_event because the description says the plan is a card in Hem and nothing is sent until tapped.

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?

Gives a clear pre-call procedure (ask what and where first, never invent a place or person) and points to whoami for resolving gang names. It does not explicitly contrast with create_event, rsvp_event, or vote_plan, so the agent must infer which sibling to use for a fixed event versus a poll.

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

All hunchful toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources