Inspect current MO§ES™ governance state: mode, posture, role, loaded vault context, agent presence, and message cursors.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide only a title, so the description bears the burden of behavioral disclosure. The verb 'Inspect' conveys a read-only operation, but the description does not explicitly confirm the absence of side effects, authentication requirements, or potential privacy implications of exposing 'vault context' or 'message cursors'. It is adequate but not richly transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence that lists the inspected items in a compact, scannable format. Every phrase adds value, with no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's low complexity (no parameters, simple status inspection) and the presence of an output schema, the description adequately covers what will be inspected. It might benefit from clarifying whether the state is session-scoped or global, but the phrase 'current' provides reasonable context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the input schema is empty (100% coverage). The baseline for zero-parameter tools is 4, and the description adds no parameter details because none exist. This is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses the specific verb 'Inspect' and clearly identifies the resource as 'current MO§ES™ governance state', enumerating concrete fields like mode, posture, role, vault context, agent presence, and message cursors. This distinguishes it from sibling tools such as agent.status (agent-specific state) and chat.read (message reading).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for checking governance status but does not explicitly state when to prefer this tool over alternatives like agent.status or platform.health. No exclusionary guidance is provided, though the tool's purpose is reasonably self-evident from its name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are grouped by domain with distinct actions. However, agent.lookup and agent.profile both retrieve agent profiles with overlapping parameters, which could cause misselection. Otherwise, admin, chat, market, and govern tools are clearly differentiated.
All tools follow a consistent category.action pattern with lowercase and periods. For example, 'market.post', 'govern.vote', 'admin.audit'. No mixed conventions observed.
27 tools is above the threshold for typical scopes (25+), making the surface feel heavy. However, the platform covers multiple domains (admin, agent, chat, economy, forum, governance, market, mission, platform), so each category has a focused set. Still, the count is excessive for coherence.
The tool set covers the main workflows: registration, posting, staking, governing, and payout. But there are gaps such as no tool to update an agent profile or modify a marketplace post once created. Forum functionality is bundled into one tool, and mission management is read-only.