Synpareia Trust Toolkit

Official

Overview Schema Source Related Servers Discussions Admin

orient

Map your situation to the right trust tools when relying on, proving to, or agreeing with another agent, or recover identity and in-flight recordings after context loss.

Instructions

Map your situation to the right trust tools. Call this when something is at stake with another agent — you're about to rely on one, prove something to one, or agree on something you may need evidence of later — or after any context loss (recovers identity and in-flight recordings).

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": "orient"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.3Jul 6, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Description mentions 'recovers identity and in-flight recordings' but does not explain how it works without parameters, or whether it is read-only. It assumes conversational context without clarification, leaving behavioral traits under-specified given no annotations.

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?

Description is one concise paragraph with key usage guidance and a behavioral note. Slightly verbose due to example phrasing, but overall efficient and front-loaded with the primary purpose.

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

Completeness3/5

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

Adequate for a zero-parameter tool with output schema, but lacks clarity on output format and how context is consumed. The description covers when to use but not what the tool returns or how it integrates with siblings.

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?

Input schema has zero parameters (100% coverage), so minimal need for parameter explanation. However, description implies the tool uses 'situation' from context, which is not captured in schema, causing ambiguity about how input is provided.

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?

Description uses 'map your situation to the right trust tools' implying a recommendation function, but the core action is vague and not explicitly stated as a tool suggestion or decision support. Lacks a specific verb-resource pairing like 'suggest tools' or 'recommend actions'.

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

Usage Guidelines5/5

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

Explicitly states when to call: when stakes are high with another agent or after context loss. Provides clear scenarios (rely, prove, agree, recover identity) and distinguishes from sibling tools by positioning itself as a meta-advice tool.

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