Atisbo

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 with atisbo_lookup mode=open, full corpus via claim depth=work, aggregates via atisbo_analyze. Edit via atisbo_lookup mode=doc_patch_context then atisbo_capture mode=patch_artefact.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	snapshot (alias: workspace) uses task; whats_new uses since_checkpoint; strategy/integrations need no IDs.
`task`	No	triage = untriaged inbox; planning = confirmed opportunities by priority; operations = signals & integrations; executive = KPIs & strategy.
`depth`	No	summary (alias: brief) = compact fields; work = full context (default).
`limit`	No	Max items. snapshot clamps to 20; whats_new to 50.
`cursor`	No	Pagination cursor.
`since_checkpoint`	No	ISO 8601 checkpoint for delta reads.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 30, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "result": {}
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedSep 27, 2026
- removedInput schema / properties / cursor / minLength
```
Removed value: -1
```
- removedInput schema / properties / limit / maximum
```
Removed value: -9007199254740991
```
Changed3 schema fields changedSep 26, 2026
- 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."
```

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / cursor / description

Previous value: -"Pagination cursor from a previous response."New value: +"Pagination cursor."

First observedSep 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered and not contradicted. The description adds the workflow-continuity rule and the snippet:// reference convention, but says nothing about pagination behavior or what the four modes actually yield beyond the schema's own mode list.

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 purpose and the mode list before the routing rules, and no sentence is redundant. It is dense with cross-tool references, but each clause carries routing information an agent needs.

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 annotations, a full output schema, and 100% parameter coverage handled elsewhere, the description only needs to supply the routing map, which it does. Minor gap: the cursor/pagination behavior and the relationship between orient and atisbo_map are left implicit.

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 every enum (mode, task, depth) is documented inline, so the schema does the heavy lifting. The description simply repeats the mode names already enumerated in the schema and adds no syntax, defaults, or interaction detail beyond it — baseline 3.

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

Purpose3/5

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

States the resource (workspace) and enumerates the four modes, giving operational sense, but the verb 'orientation' is vague and borders on restating the tool name. Sibling differentiation is partial: it names atisbo_lookup, atisbo_analyze, and atisbo_capture for adjacent tasks, which implicitly scopes what orient is not, yet it never plainly says what orient returns.

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 rule 'Continue the user's existing workflow; never create a parallel backlog' is a genuine usage constraint, and the routing sentences point to other tools for opening docs, corpus reads, and edits. However, there is no explicit statement of when to choose orient over siblings like atisbo_map or atisbo_analyze, only a description of what those siblings do.

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

All Atisbo tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?