Skip to main content
Glama
Sign In
continuityos

continuityos

by bitmaster162
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_frontier

Set the active focus for trunk, cash, lab, or parked by designating an item. Maintains one focus per domain for continuity.

Instructions

Set the trunk/cash/lab/parked focus (1 trunk + 1 cash + 1 lab discipline).

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": {
      "kind": "<kind>",
      "item": "<item>"
    },
    "name": "set_frontier"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

A3.5/5.0
Behavior3/5

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

The description discloses the one-per-category constraint, but with no annotations, it fails to disclose other behavioral aspects like whether it overwrites existing focus, whether the operation is reversible, or what happens if the constraint is violated.

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?

The description is a single concise sentence with no unnecessary words. It efficiently includes the key constraint without padding.

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 no annotations and no output schema, the description is incomplete for effective use. It fails to explain what 'item' should be, what format it expects, or what the outcome of the operation is beyond setting focus.

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 coverage is 0%, and the description does not explain the 'item' parameter at all. It only indirectly clarifies 'kind' via the focus categories, leaving the required 'item' parameter ambiguous.

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 action ('Set') and the resource ('trunk/cash/lab/parked focus') with a specific constraint. This distinguishes it from sibling tools, which deal with memory, context, or other functions.

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 by stating what the tool does and includes a constraint (1 trunk + 1 cash + 1 lab discipline), but it does not explicitly mention when to use it versus alternatives or any exclusions.

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

Deploy Server

Other Tools