Skip to main content
Glama

polarity_checkin

Records your check-in at a waypoint and triggers co-presence detection to find nearby users who checked in recently.

Instructions

Record that the user checked in at a waypoint. Triggers co-presence detection against other users' recent check-ins.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waypoint_idYes
nameYes
latNo
lonNo
occurred_atNo

Implementation Reference

  • The TOOLS array where all tools including polarity_checkin are registered.
    export const TOOLS: ToolDef[] = [
  • The tool definition for polarity_checkin including name, description, and inputSchema (waypoint_id, name, lat?, lon?, occurred_at?).
    {
      name: "polarity_checkin",
      description:
        "Record that the user checked in at a waypoint. Triggers co-presence detection against other users' recent check-ins.",
      inputSchema: z
        .object({
          waypoint_id: z.string().min(1).max(128),
          name: z.string().min(1).max(128),
          lat: z.number().optional(),
          lon: z.number().optional(),
          occurred_at: z.string().datetime().optional(),
        })
        .strict(),
  • The handler lambda that delegates to client.checkin(...).
    handler: async (input, client) => client.checkin(input as Parameters<CosmosClient["checkin"]>[0]),
  • CosmosClient.checkin() method that makes the HTTP POST to /api/polarity/checkin.
    checkin(input: { waypoint_id: string; name: string; lat?: number; lon?: number; occurred_at?: string }) {
      return this.request<unknown>({
        method: "POST",
        path: "/api/polarity/checkin",
        body: { polarity_user_id: this.config.polarityUserId, ...input },
      });
    }
Behavior3/5

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

With no annotations, the description carries full burden. It discloses the recording and co-presence trigger, but lacks details on side effects like idempotency, data persistence, or privacy implications. Basic disclosure but incomplete.

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

Conciseness5/5

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

Two concise sentences with no wasted words. The purpose and key behavioral aspect are front-loaded. Efficient use of space for high-impact information.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 5 parameters, no output schema, and no annotations, the description should cover return value, sequencing, or constraints. It only mentions the side effect. Incomplete for a tool with this complexity.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It adds no explanation beyond parameter names, which are somewhat self-explanatory. No guidance on formatting, optionality, or relationships between parameters.

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 clearly states the tool records a check-in at a waypoint and triggers co-presence detection. The verb 'record' and resource 'waypoint' are specific, and the side effect distinguishes it from siblings like polarity_observe or polarity_record_event.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you want to record a check-in and trigger co-presence detection, but it does not explicitly state when not to use it or mention alternatives. The co-presence mention gives context, but no direct guidance on tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/teampolarity/cosmos-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server