Skip to main content
Glama

Orient: workspace snapshot and workflow state

atisbo_orient
Read-only

Workspace orientation. Modes: snapshot, whats_new, strategy, integrations. Continue the user's existing workflow; never create a parallel backlog. Living docs cite snippet:// refs — open atisbo_lookup mode=open; corpus via claim depth=work; aggregates via atisbo_analyze; edit via atisbo_lookup mode=doc_patch_context then atisbo_capture mode=patch_artefact (living documents; manual Knowledge documents are edited in place with atisbo_capture mode=update_artefact).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "atisbo_orient"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNosnapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none. Open string (new modes work with a cached tools/list); unknown mode? invalid_params[].allowed_values names the nearest.
taskNotriage=untriaged inbox; planning=confirmed opportunities by priority; operations=signals & integrations; executive=KPIs & strategy.
depthNosummary=compact; work=full (default).
limitNoMax items. snapshot clamps to 20; whats_new to 50.
cursorNoPagination cursor.
since_checkpointNoISO 8601 checkpoint for delta reads.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / depth / enum
      Previous value: -[
      -  "summary",
      -  "work"
      -]New value: +[
      +  "summary",
      +  "work",
      +  "brief"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none. Open string, not a closed enum: a mode added after your tools/list was cached still reaches the server; unknown mode? The nearest accepted value and full list answer in invalid_params[].allowed_values."New value: +"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none. Open string (new modes work with a cached tools/list); unknown mode? invalid_params[].allowed_values names the nearest."
  3. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none. Open string, not a closed enum: a mode added after your tools/list was cached still reaches the server. An unknown mode answers with the nearest accepted value and the full list in invalid_params[].allowed_values."New value: +"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none. Open string, not a closed enum: a mode added after your tools/list was cached still reaches the server; unknown mode? The nearest accepted value and full list answer in invalid_params[].allowed_values."
  4. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none."New value: +"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none. Open string, not a closed enum: a mode added after your tools/list was cached still reaches the server. An unknown mode answers with the nearest accepted value and the full list in invalid_params[].allowed_values."
    • removedInput schema / properties / mode / enum
      Removed value: -[
      -  "snapshot",
      -  "whats_new",
      -  "strategy",
      -  "integrations"
      -]
  5. Changed3 schema fields changed
    • changedInput schema / properties / depth / description
      Previous value: -"summary (alias: brief) = compact fields; work = full context (default)."New value: +"summary=compact; work=full (default)."
    • changedInput schema / properties / mode / description
      Previous value: -"snapshot (alias: workspace) uses task; whats_new uses since_checkpoint; strategy/integrations need no IDs."New value: +"snapshot (alias: workspace)=task; whats_new=since_checkpoint; strategy/integrations none."
    • changedInput schema / properties / task / description
      Previous value: -"triage = untriaged inbox; planning = confirmed opportunities by priority; operations = signals & integrations; executive = KPIs & strategy."New value: +"triage=untriaged inbox; planning=confirmed opportunities by priority; operations=signals & integrations; executive=KPIs & strategy."
  6. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "result": {}
      +  },
      +  "required": [
      +    "result"
      +  ],
      +  "type": "object"
      +}
  7. Changed2 schema fields changed
    • removedInput schema / properties / cursor / minLength
      Removed value: -1
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  8. Changed3 schema fields changed
    • addedInput schema / properties / limit / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / since_checkpoint / description
      Previous value: -"ISO 8601 checkpoint for delta reads; invalid values are ignored."New value: +"ISO 8601 checkpoint for delta reads."
  9. Changed1 schema field changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Pagination cursor from a previous response."New value: +"Pagination cursor."
  10. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds genuine behavioral context beyond that: the workflow-continuity constraint against spawning a parallel backlog, and the distinction between living documents (patched via patch_artefact) and manual Knowledge documents (edited in place via update_artefact). It does not discuss pagination or delta semantics beyond what the schema states.

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

Conciseness3/5

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

It is front-loaded with the core purpose and modes, which is good, but it devolves into a dense run-on chain of sibling-tool routing, including doc-editing paths that belong to atisbo_capture rather than this read-only orient tool. Much of that routing is useful, yet the editing instructions feel tangential to what this tool does.

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 six optional parameters, full schema coverage, and an output schema handling return values, the definition supplies enough to call the tool correctly and to hand off follow-up work to the right sibling. What is missing is minor: which mode is the sensible default and what triggers each mode in practice.

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

Parameters3/5

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

Schema description coverage is 100% and both enums (mode, task) are fully documented in the schema, so the baseline is 3. The description adds only a light semantic tie, indicating that corpus reads use depth=work; it does not otherwise clarify limit clamping, cursor usage, or since_checkpoint beyond the schema's own text.

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?

The description opens with "Workspace orientation" and enumerates the four modes (snapshot, whats_new, strategy, integrations), which tells an agent this tool returns workspace/workflow state rather than records. It also implicitly separates itself from siblings by routing lookups to atisbo_lookup, aggregates to atisbo_analyze, and writes to atisbo_capture. The only gap is that "orientation" is an abstract noun rather than a crisp verb+resource statement.

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 gives an explicit usage directive ("Continue the user's existing workflow; never create a parallel backlog") and names concrete alternatives with the specific modes that select them: atisbo_lookup mode=open for snippet refs, atisbo_analyze for aggregates, atisbo_lookup mode=doc_patch_context plus atisbo_capture mode=patch_artefact for edits. It stops short of stating the entry condition (e.g. call this first at session start), so the when-to-invoke-this specifically is still inferred.

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.

Resources